www/server/standards/translations details.html

[Yavor Doganov]

CVSROOT:        /web/www
Module name:    www
Changes by:     Yavor Doganov <yavor>   07/12/29 13:34:47

Modified files:
        server/standards/translations: details.html 

Log message:
        (Updating to the new style): New section.
        (Mailing lists): Restore www-discuss, it is compulsory for team
        leaders.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/translations/details.html?cvsroot=www&r1=1.2&r2=1.3

Patches:
Index: details.html
===================================================================
RCS file: /web/www/www/server/standards/translations/details.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- details.html        24 Nov 2007 10:38:11 -0000      1.2
+++ details.html        29 Dec 2007 13:34:40 -0000      1.3
@@ -1,7 +1,7 @@
 <!--#include virtual="/server/header.html" -->
 <title>Web Translation Details - GNU Project - Free Software Foundation 
(FSF)</title>
 <!--#include virtual="/server/banner.html" -->
-<h1>Web Translation Details</h1>
+<h2>Web Translation Details</h2>
 
 <p>This is a detailed description of translation processes for
 <a href="/">the GNU website</a>, so everyone can quickly get
@@ -11,7 +11,7 @@
 
 <!-- ---------------------------------------------------------------- -->
 
-<h2>Introduction</h2>
+<h3>Introduction</h3>
 <p>The GNU website has thousands of documents, most of them
 philosophical articles and technical documents which need
 to be translated to get them available to a broader audience,
@@ -22,7 +22,7 @@
 </p>
 
 
-<h2>Web Translators</h2>
+<h3>Web Translators</h3>
 <p>Translators should work on translating web pages according
 to the <a href="/server/standards/">GNU Web Standards</a>
 designed by webmasters and sysadmins at GNU.  Among many other
@@ -45,7 +45,67 @@
 <p>Please, see also
 <a href="trans-team-member.html">how to join a web translation team</a>.
 
-<h2>Web Translation Teams</h2>
+<h4>Updating to the new style</h4>
+
+<p>The new style of the gnu.org website relies on SSI (Server Side
+Includes) which makes it easy to propagate important changes to all
+pages, as well as maintain a uniform look &amp; feel.  It is easier
+for translators, because they deal with less markup.  To update your
+translations you have to translate the &ldquo;templates&rdquo;:
+</p>
+
+<ol>
+<li>Copy <tt>/graphics/topbanner.svg</tt>
+  to <tt>/graphics/topbanner.xx.svg</tt> where &ldquo;xx&rdquo; is the
+  language code.  Edit the file with Inkscape or with a plain text
+  editor such as <a href="/software/emacs">GNU Emacs</a>, translating
+  &ldquo;GNU Operating System&rdquo;.  Then with Inkscape, save the
+  file as <tt>/graphics/topbanner.xx.png</tt> (<kbd>File -&gt; Export
+  Bitmap&hellip;</kbd>).  Then open the PNG image with the GIMP and
+  flatten it (<kbd>Image -&gt; Flatten Image</kbd>).  Don't forget to
+  save and <tt>cvs add</tt> the files &mdash; this applies to all
+  new files, of course.
+</li>
+<li>Create a <tt>style.xx.css</tt> in the root.  Normally, you would
+  need only one line in it,
+  namely <br />
+  <code>#logo{background:url(/graphics/topbanner.xx.png) no-repeat;}</code>
+</li>
+<li>Translate <tt>/server/header.html</tt>.  Basically this means
+  substituting the attributes &ldquo;xml:lang&rdquo; and
+  &ldquo;lang&rdquo;, specifying the proper encoding and inserting the
+  appropriate line as
+  per <a href="/server/standards/README.translations.html#TOC9">this
+  note</a>.
+</li>
+<li>Translate <tt>/server/banner.html</tt>, <tt>/server/footer.html</tt>
+  and <tt>/server/footer-text.html</tt>.
+  In <tt>/server/banner.xx.html</tt>, you have to import your CSS
+  style on the third line, for example: <br />
+  <pre>
+  &lt;style type="text/css" media="all"&gt;
+  @import url('/style.css');
+  @import url('/style.xx.css');
+  &lt;/style&gt;
+  </pre>
+</li>
+<li>Adjust the markup of your translations to be valid XHTML and add
+  the appropriate directives.
+</li>
+</ol>
+
+<p>If you are updating from the previous SSI-fied look with the
+sidebar, note that these files under <tt>/server</tt> are no longer
+needed and can be deleted: <tt>style.xx.css</tt> (if any),
+<tt>footer-short.xx.html</tt> and <tt>footer-min.xx.html</tt>
+(provided that you change all your pages not to use them),
+<tt>sidebar.xx.html</tt>, <tt>sidebar-bottom-half.xx.html</tt>,
+<tt>sidebar-fsf-support.xx.html</tt>, <tt>sidebar-short.xx.html</tt>,
+<tt>sidebar-min.xx.html</tt>, <tt>sidebar-stay.xx.html</tt>,
+<tt>sidebar-bottom-half.xx.html</tt>.
+</p>
+
+<h3>Web Translation Teams</h3>
 <p>Each language present on the GNU website should have
 a team, however some translations were volunteered by
 people who didn't want to take charge of a team; hence,
@@ -92,7 +152,7 @@
 If a member makes a translation, he has to review another one (or two)
 as well.</p>
 
-<h3>Savannah</h3>
+<h4>Savannah</h4>
 <p>Every translation team should have a project in
 <a href="http://savannah.gnu.org/";>Savannah</a>.  For
 historical reasons those team names may vary a lot (e.g.
@@ -112,7 +172,7 @@
 CVS, home pages, mailing lists, etc.  How each uses
 these resources it's up to the team itself.</p>
 
-<h3>Mailing lists</h3>
+<h4>Mailing lists</h4>
 <p>Mailing lists usually are linked to existing Savannah
 projects, but the software used to manage them
 (<a href="/software/mailman/">Mailman</a>)
@@ -120,7 +180,7 @@
 that aren't linked to any specific project, though may be
 related to some.</p>
 
-<h3>Aliases</h3>
+<h4>Aliases</h4>
 <p>On the other side, people with an account in GNU servers
 usually can update existing team aliases (e.g. web-translators-fr).
 However, this isn't recommended unless you know exactly
@@ -128,7 +188,7 @@
 on this and will take care of updating aliases at leader's
 request.</p>
 
-<h3>Team Leaders</h3>
+<h4>Team Leaders</h4>
 <p>People in charge of a translation team are team leaders
 and Savannah project admins.  Usually, they're the only
 people from their team with write CVS access to the GNU website,
@@ -138,14 +198,14 @@
 <a href="trans-coordinator.html">how to coordinate a translation team</a>.
 </p>
 
-<h2>Web Translation Managers</h2>
+<h3>Web Translation Managers</h3>
 <p>Translation managers are those people coordinating
 translation coordinators (team leaders) and dealing with
 all sort of requests or issues related to GNU website
 translation, while trying to improve the translation
 procedures and coodinating with GNU webmasters, too.</p>
 
-<h3>Request Tracker (RT)</h3>
+<h4>Request Tracker (RT)</h4>
 <p><a href="http://www.bestpractical.com/rt/";>Request Tracker</a>
 is a ticketing system that helps managing translation
 requests and issues to translation managers.  It's the
@@ -166,7 +226,7 @@
 web-translators-admin group, but anyone in group
 web-translators-staff can use it to tag tickets.</p>
 
-<h3>Savannah</h3>
+<h4>Savannah</h4>
 
 <ol>
 <li><a href="https://savannah.gnu.org/p/www";>www</a></li>
@@ -175,11 +235,12 @@
 <li>Savannah administration</li>
 </ol>
 
-<h3>Mailing Lists</h3>
+<h4>Mailing Lists</h4>
 <p>There are a few mailing lists that every translation
 manager should be subscribed to:</p>
 
 <ol>
+<li>www-discuss</li>
 <li>www-commits (admin)</li>
 <li>trans-coord-discuss (member+admin)</li>
 <li>trans-coord-news (admin)</li>
@@ -188,16 +249,16 @@
 <p>Some of them, will need that some translation managers
 become their admins too (as noted above).</p>
 
-<h3>Aliases</h3>
+<h4>Aliases</h4>
 <p>Translation managers should know how to update, create
 or remove aliases from GNU servers per request of translation
 team leaders.  An account in GNU servers is a prerequisite.</p>
 
-<h3>To Do</h3>
+<h4>To Do</h4>
 Some tasks <a href="todo.txt">to do</a> were recorded.
 Need more work.
 
-<h3>Draft Procedures</h3>
+<h4>Draft Procedures</h4>
 Some common <a href="draft-procedures.txt">procedures</a>
 were drafted.  Need more work.
 
@@ -236,7 +297,7 @@
 <p>
 Updated:
 <!-- timestamp start -->
-$Date: 2007/11/24 10:38:11 $
+$Date: 2007/12/29 13:34:40 $
 <!-- timestamp end -->
 </p>
 </div>