www/server/staging/translations README.translat...

[Dora Scilipoti]

CVSROOT:        /web/www
Module name:    www
Changes by:     Dora Scilipoti <dora>   11/12/29 10:57:02

Modified files:
        server/staging/translations: README.translations.html 

Log message:
        Revised.

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

Patches:
Index: README.translations.html
===================================================================
RCS file: /web/www/www/server/staging/translations/README.translations.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- README.translations.html    27 Dec 2011 14:16:28 -0000      1.2
+++ README.translations.html    29 Dec 2011 10:56:57 -0000      1.3
@@ -82,8 +82,7 @@
       organizing the work. Thus, to join an existing team, you need to get
       detailed information from that team. The Team Coordinator will be
       able to guide you through their specific methods. If you don't get an
-      answer <del>[delete]from the team</del> in two weeks, write to the 
-      Translations Manager <a
+      answer in two weeks, write to the Translations Manager <a
       href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
     </dd>
 
@@ -97,12 +96,12 @@
       if there is no team or coordinator for your language.</dd>
 
   <dt>As a Team Coordinator</dt>
-    <dd><ins>If there is no team established for your language or a new Team 
+    <dd>If there is no team established for your language or a new Team 
       Coordinator is needed, we will be grateful if you undertake that task. 
       As a coordinator, you will need to follow both the <a 
       href="#general-guide">General Guide for Translations</a>  and the more 
       specific <a href="#coordinator-guide">Guide for Team Coordinators.</a>
-      </ins></dd>
+      </dd>
 </dl>
 
 <h3 id="general-guide">General Guide for Translations</h3>
@@ -150,14 +149,6 @@
     Unix</span>)&rdquo;.</p></li>
 </ul>
 
-<h4 id="translators-manual">Translators Manual</h4>
-
-<p>You may also want to read the <a
-href="/software/trans-coord/manual/web-trans/">GNU Web Translators
-Manual</a> if you wish to have a better understanding of how our
-translation system works. But please talk to the team first; most probably
-you will not be required to read it in order to start helping.</p>
-
 <h4 id="what">What to Translate</h4>
 
 <p>All essays and articles in the following directories should be
@@ -182,66 +173,71 @@
 something in that directory, please talk with the maintainers of the package 
 to see what they would like to do.</p>
 
+<h4 id="translators-manual">Translators Manual</h4>
+
+<p>You may also want to read the <a
+href="/software/trans-coord/manual/web-trans/">GNU Web Translators
+Manual</a> if you wish to have a better understanding of how our
+translation system works. But please talk to the team first; most probably
+you will not be required to read it in order to start helping.</p>
+
+
 <h3 id="coordinator-guide">Guide for Team Coordinators</h3>
 
-<p><ins>The following is an explanation of what a Team Coordinator does 
+<p>The following is an explanation of what a Team Coordinator does 
 specifically. In addition to what has already been described, a Team 
-Coordinator:</ins></p>
+Coordinator:</p>
 
 <ul>
-  <li><p><ins>sees to it that all texts to be published are faithful to the 
+  <li><p>sees to it that all texts to be published are faithful to the 
     original and respect the terminology used in our website. All 
     translations submitted by team members or by occasional contributors are 
     reviewed and approved by the Team Coordinator before they are 
-    published;</ins></p></li>
+    published;</p></li>
 
   <li><p><ins>understands thoroughly how our translation system works, and 
-    knows how to use the tools that we have adopted. Basically, the whole 
-    translation process revolves around GNUNited Nations (GNUN), the very 
-    useful program we mentioned at the beginning of this page. Let's see 
-    briefly in the following section how we handle the translations of our 
-    pages and how we keep them current.</ins></p></li>
+    knows how to use the tools that we have adopted. In the following section 
+    we explain briefly how it is done.</ins></p></li>
 </ul>
 
-<h4 id="tools">Tools <del>[delete] to Help Translators</del></h4>
+<h4 id="tools">Tools</h4>
 
 <p>We use .po (Portable Object) files to process and maintain translations. 
 A .po file contains the original text and its translation, divided in 
 paragraphs. This is how we do it:</p>
 
 <ul>
-  <li><p><ins>When a new article is published in our website, GNUN generates 
-    a .pot file (.po template) from that article. The .pot file is renamed 
-    to .po to be translated. Once it is translated, the .po file is committed. 
-    Then GNUN checks it, and if there are no errors in the code, the 
-    translated HTML version of the original article is automatically 
-    published in the website.</ins></p></li>
+  <li><p><ins>When a new article is published in our website, GNUN, the 
+    program we mentioned at the beginning of this page, generates a .pot file 
+    (.po template) from that article. The .pot file is renamed to .po to be
+    translated. Once it is translated, the .po file is committed. Then
+    GNUN checks it, and if there are no errors in the code, the translated
+    HTML version of the original article is automatically published in the
+    website.</ins></p></li>
 
-  <li><p><ins>Whenever there is a change in the original HTML article, the 
+  <li><p>Whenever there is a change in the original HTML article, the 
     .pot and .po files are regenerated by GNUN to merge the changes, clearly 
     showing the strings that have changed. Translators then update the 
     translation of only those strings in the .po file. When the updated .po 
     file is committed, the HTML version of the translation is automatically 
-    updated on the website.</ins></p></li>
+    updated on the website.</p></li>
 
-  <li><p><ins>.po files can be edited by using</ins> <a 
-    href="/software/emacs/">GNU Emacs</a> (installing <em>gettext-el</em> to 
-    automatically switch to PO mode) or any .po file editor.</p>
+  <li><p><ins>.po files can be edited by using any .po file editor.</ins></p>
 </ul>
 
-<p><ins>We have also implemented notification tools to keep translators
+<p>We have also implemented notification tools to keep translators
 informed of changes in the original pages. In any case, a Team
 Coordinator needs to subscribe to our <a
 href="http://lists.gnu.org/mailman/listinfo/www-commits";>www-commits</a>
-mailing list to keep an eye on pages that are modified.</ins> You may also
+mailing list to keep an eye on pages that are modified. You may also
 use &ldquo;<em><code>make report TEAM=LANG</code></em>&rdquo; if you
 have GNUN installed.</p>
 
-<h4 id="coord-manuals"><ins>Coordinators Manuals</ins></h4>
+<h4 id="coord-manuals">Coordinators Manuals</h4>
 
-<p><ins>The following manuals explain in detail the translation process that 
+<p>The following manuals explain in detail the translation process that 
 we have briefly shown above. It is necessary that a coordinator reads and 
-becomes well acquainted with them:</ins></p>
+becomes well acquainted with them:</p>
 
 <ul>
   <li><a href="/software/trans-coord/manual/web-trans/">GNU Web
@@ -254,12 +250,12 @@
   Guidelines: HTML Style Sheet</a></li>
 </ul>
 
-<p><ins>After you have read this entire page, if you intend to volunteer and 
-be listed as the <del>[delete]translation</del> Team Coordinator for your 
-language, please inform the Translations Manager <a
+<p>After you have read this entire page, if you intend to volunteer and 
+be listed as the Team Coordinator for your language, please inform the 
+Translations Manager <a
 href="mailto:address@hidden";>&lt;address@hidden&gt;</a>
 of your decision. Start reading at least the first two manuals and ask
-the Translations Manager for assistance if you have any doubts.</ins></p>
+the Translations Manager for assistance if you have any doubts.</p>
 
 <h3 id="teams">Translation Teams</h3>
 <span id="TranslationsUnderway"><!--Some docs refer to this anchor--></span> 
@@ -267,14 +263,8 @@
 <p>Volunteers to establish new teams are more than welcome and will be
 assisted during the learning process.</p>
 
-<p><del>[delete]Contact the Translations Manager <a
-href="mailto:address@hidden";>&lt;address@hidden&gt;</a>
-if you would like to form a new team or become a Team Coordinator and be
-listed as the translation Team Coordinator for your language.</del></p>
-
 <p>In the following list, the language code is followed by the name of the
-language, and by the name <del>[delete]and contact details</del> of the 
-<del>[delete]translation</del> Team Coordinator.</p>
+language, and by the name of the Team Coordinator.</p>
 <ul>
   <!-- Please keep this list alphabetical-->
   <li><code>ar</code> - <a
@@ -419,10 +409,9 @@
 
 <p><strong>Note:</strong> <em>English</em> (<code>en</code>)is a special
 case. The bulk of the site is written in English, which is the de-facto
-language of the GNU Project. We <em>occasionally</em> need <ins>to 
-translate to English original documents written in other languages.</ins> It 
-is best to notify the Team Coordinator <ins>of that language if you 
-volunteer.</ins> <del>[delete]because we always contact them first.</del> If 
+language of the GNU Project. We <em>occasionally</em> need to 
+translate to English original documents written in other languages. It 
+is best to notify the Team Coordinator of that language if you volunteer. If 
 there is no team coordinator and you are willing to help with this, please 
 contact <a 
 href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
@@ -450,7 +439,7 @@
 
 <p>Updated: 
 <!-- timestamp start -->
-$Date: 2011/12/27 14:16:28 $
+$Date: 2011/12/29 10:56:57 $
 <!-- timestamp end --></p>
 </div>
 </div>