www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Dora Scilipoti
Subject: www/server/staging/translations README.translat...
Date: Tue, 27 Dec 2011 14:16:35 +0000

CVSROOT:        /web/www
Module name:    www
Changes by:     Dora Scilipoti <dora>   11/12/27 14:16:35

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

Log message:
        Introducing changes.

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

Patches:
Index: README.translations.html
===================================================================
RCS file: /web/www/www/server/staging/translations/README.translations.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- README.translations.html    19 Dec 2011 18:11:17 -0000      1.1
+++ README.translations.html    27 Dec 2011 14:16:28 -0000      1.2
@@ -1,37 +1,37 @@
 <!--#include virtual="/server/html5-header.html" -->
+
 <!-- Parent-Version: 1.63 -->
-<title>Guide to Translating Web Pages on www.gnu.org 
-- GNU Project - Free  Software Foundation (FSF)</title>
-  <style type="text/css">
+
+<title>Guide to Translating Web Pages on www.gnu.org - GNU Project - Free  
+Software Foundation (FSF)</title>
+
+<style type="text/css">
 del { background-color:#FFDDDD; margin:0px;}
 ins { background-color:#FFFF66; margin:0px;}
 </style>
+
 <!--#include virtual="/server/banner.html" -->
 <!--#include virtual="/server/standards/po/README.translations.translist" -->
-<h2 id="guide" class="section">Guide to Translating Web Pages on
-www.gnu.org</h2>
 
-<p>Draft: 2011-11-14 | Last update:
-<!--$date=-->2011-12-16<!--$--></p>
+<h2 id="guide" class="section">Guide to Translating Web Pages on 
www.gnu.org</h2>
 
 <p><a href="/graphics/atypinggnu.html"><img style="float: right;"
 src="/graphics/gnu-type-sm.jpg" alt="A Typing GNU"
 title="A Typing GNU Hacker" /></a></p>
-<!--h3 id="general">General Guide</h3-->
 
 <h3 id="intro">Introduction</h3>
 
 <p>Translating gnu.org with its many articles and keeping them updated is a
 complex task which requires careful organization. Translators are grouped
-into teams, one for each language, and each team normally has a
-coordinator. However, there are some languages for which no team has been
-formed yet, and sometimes a team lacks a coordinator.</p>
+into teams, one for each language, and each team normally has a coordinator. 
+However, there are some languages for which no team has been formed yet, and 
+sometimes a team lacks a coordinator.</p>
 
 <p>Team Coordinators use software tools to update pages efficiently for
-partial changes. One of these tools is a program called <strong>GNUnited
-Nations</strong> (GNUN) that makes it very easy to maintain and keep track
-of translations that need to be updated; it was developed ad hoc by our
-current GNU Translations Manager Yavor Doganov.</p>
+partial changes. One of these tools is a program called GNUnited Nations 
+(GNUN) that makes it very easy to maintain and keep track of translations 
+that need to be updated; it was developed ad hoc by our current GNU 
+Translations Manager Yavor Doganov.</p>
 
 <p>The Translations Manager is the person in charge of the overall
 organization of teams and is generally involved in training new Team
@@ -47,15 +47,18 @@
 task for everyone in the translation process: we need people with good
 language skills, as well as people with good technical skills or willing to
 learn some simple technical skills.</p>
+
 <ul>
   <li><p>If you have a deep understanding of written English and a rich
     command of your native language, you can certainly engage in
     translation, or do proof-reading. Writing good English is not
   necessary.</p></li>
+
   <li><p>If your understanding of English is not first class, or if you don't
     know English at all but have a good mastery of your mother tongue, you
     can help review other people's translations to make sure they read well
     and have a good style.</p></li>
+
   <li><p>If you are a native English speaker, and you can read another
     language, even if not quickly and easily, you can still help improve
     translations in that language. Translators sometimes misunderstand
@@ -63,6 +66,7 @@
     misleading or even incorrect. These errors are obvious to the native
     English speaker&mdash;you can indicate possible errors and explain the
     intended meaning, and others can retranslate that part.</p></li>
+
   <li><p>If you are inclined or willing to go for the more technical side of
     the translation process, you can help further; for example, by
     preparing translated texts for publication.</p></li>
@@ -78,10 +82,11 @@
       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 from the team in two weeks, write to the Translations Manager
-      <a
+      answer <del>[delete]from the team</del> in two weeks, write to the 
+      Translations Manager <a
       href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
     </dd>
+
   <dt>As an Occasional Contributor</dt>
     <dd>If you just want to submit a new translation and are not interested
       in collaborating regularly, follow the <a
@@ -90,11 +95,14 @@
       Coordinator</a> if there is one, or to the Translations Manager <a
       href="mailto:address@hidden";>&lt;address@hidden&gt;</a>
       if there is no team or coordinator for your language.</dd>
+
   <dt>As a Team Coordinator</dt>
-    <dd>If you would like to form a new team or become a Team Coordinator,
-      please read this entire page and then get in touch with the
-      Translations Manager <a
-      href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</dd>
+    <dd><ins>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>
 </dl>
 
 <h3 id="general-guide">General Guide for Translations</h3>
@@ -116,11 +124,14 @@
     languages. You will see that in most cases it has not been translated
     at all, so if you can't find a good translation for it in your
     language, the only option may be to use the English word.</p></li>
+
   <li><p>See the <a href="/philosophy/fs-translations.html">Translations of
     the Term  &ldquo;Free Software&rdquo;</a> in several languages.</p></li>
+
   <li><p>You can learn more about specific terms and the GNU philosophy by
     reading some articles such as the following, among others that you may
     find useful:</p>
+
     <ul>
       <li><a href="/philosophy/free-sw.html">What is Free Software?</a></li>
       <li><a href="/philosophy/categories.html">Categories of Free and
@@ -131,6 +142,7 @@
         Source Misses the Point of Free Software</a></li>
     </ul>
   </li> 
+
   <li><p>When translating &ldquo;GNU's Not Unix&rdquo;, please ensure that the
     translation remains recursive. If a recursive translation cannot be
     conceived, use the following format (this is an example for Swedish):
@@ -152,6 +164,7 @@
 translated in all available languages, but you should first browse our <a
 href="/server/standards/translations/priorities.html">Web Translation
 Priorities</a>:</p>
+
 <ul>
   <li><code>copyleft/</code></li>
   <li><code>education/</code></li>
@@ -164,91 +177,89 @@
 work, to get clear instructions on how to proceed and to avoid duplicating
 efforts.</p>
 
-<p><em><strong>Note:</strong></em> The material in the
-<code>software/</code> directory pertains to individual GNU packages. If
-you would like to translate something in that directory, please talk with
-the maintainers of the package to see what they would like to do.</p>
+<p><em><strong>Note:</strong></em> The material in the <code>software/</code> 
+directory pertains to individual GNU packages. If you would like to translate 
+something in that directory, please talk with the maintainers of the package 
+to see what they would like to do.</p>
 
 <h3 id="coordinator-guide">Guide for Team Coordinators</h3>
 
-<p><em>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. To
-volunteer, write to the Translations Manager <a
-href="mailto:address@hidden";>&lt;address@hidden&gt;</a>,
-but please first read the following explanation of what a Team Coordinator
-does specifically, apart from what has been described in the General
-Guide.</em></p>
-
-<p>[option 1:]</p>
-<p>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. <ins>To
-volunteer, please first read the Guide for Team Coordinators in addition 
-to the General Guide. If you are interested, write to the Translations Manager 
<a
-href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
-</ins></p>
-
-<p>[option 2:]</p>
-<p><ins>For the case there</ins>[If there]<ins> is no team established for 
-your language or a new Team Coordinator is needed, you will be welcome to 
-undertake that task. To volunteer, please first read the following 
-explanation[statement], in addition to the General Guide.</ins></p>
-
+<p><ins>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>
 
 <ul>
-  <li>First, let's look at the tools that we use in our website to process
-    translations and to keep them updated.</li>
+  <li><p><ins>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>
+
+  <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>
 </ul>
 
-<h4 id="tools">Tools to Help Translators</h4>
+<h4 id="tools">Tools <del>[delete] to Help Translators</del></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. We do it this way so that, when there is a change in the
-English version of a page, our system will generate an updated .po file
-showing the strings that have changed. The translator then updates the
-translation of those strings.</p>
-
-<p>To edit a .po file, use <a href="/software/emacs/">GNU Emacs</a> (install
-<em>gettext-el</em> to automatically switch to PO mode) or any .po file
-editor.</p>
-
-<p>How is the .po file used? GNUnited Nations (GNUN), a build system for
-www.gnu.org translations, generates a .pot file (.po template) of an
-original HTML article; whenever there is a change in the original article,
-the .pot file is regenerated to merge the changes. Finally, it regenerates
-the translations in HTML format. For further information see <a
-href="/software/gnun/">GNUnited Nations (GNUN)</a>.</p>
-
-<h4 id="keeping-current">Keeping Translations Current</h4>
+paragraphs. This is how we do it:</p>
 
-<p>For all translations to be kept current, if you decide to become a Team
-Coordinator, you should subscribe to the <a
-href="http://lists.gnu.org/mailman/listinfo/www-commits";>www-commits</a>
-mailing list. Then you will be sent one email for each page that is
-modified in <em>CVS</em> (for the www module). The traffic is around 4-5
-mails per day, more on weekends. It's suggested that you burst through them
-about once a week to make sure the translations are current. You may also
-use &ldquo;<em><code>make report TEAM=LANG</code></em>&rdquo; if you have <a
-href="/software/gnun/">GNUN</a> installed.</p>
 <ul>
-  <li>A coordinator should also read and be well acquainted with the
-    following documentation:</li>
+  <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>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>
+
+  <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>
 </ul>
+
+<p><ins>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
+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>
+
+<p><ins>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>
+
 <ul>
-  <li><a href="/software/trans-coord/manual/web-trans/">GNU Web Translators
-    Manual</a>.</li>
-  <li><a href="/software/trans-coord/manual/gnun/">GNUnited Nations (GNUN)
-    Manual</a>,</li>
+  <li><a href="/software/trans-coord/manual/web-trans/">GNU Web
+  Translators Manual</a></li>
+  <li><a href="/software/trans-coord/manual/gnun/">GNUnited Nations
+  (GNUN) Manual</a></li>
   <li><a href="/server/standards/readme_index.html">GNU Web Site
     Guidelines: For Volunteers</a></li>
-  <li><a href="/server/fsf-html-style-sheet.html">GNU Web Site Guidelines:
-    HTML Style Sheet</a>.</li>
+  <li><a href="/server/fsf-html-style-sheet.html">GNU Web Site
+  Guidelines: HTML Style Sheet</a></li>
 </ul>
 
-<p>After you have read at least the first two manuals and this entire page,
-please contact the Translations Manager <a
+<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
 href="mailto:address@hidden";>&lt;address@hidden&gt;</a>
-for further assistance.</p>
+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>
 
 <h3 id="teams">Translation Teams</h3>
 <span id="TranslationsUnderway"><!--Some docs refer to this anchor--></span> 
@@ -256,14 +267,14 @@
 <p>Volunteers to establish new teams are more than welcome and will be
 assisted during the learning process.</p>
 
-<p>Contact the Translations Manager <a
+<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.</p>
+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 and contact details of the translation Team
-Coordinator.</p>
+language, and by the name <del>[delete]and contact details</del> of the 
+<del>[delete]translation</del> Team Coordinator.</p>
 <ul>
   <!-- Please keep this list alphabetical-->
   <li><code>ar</code> - <a
@@ -406,17 +417,19 @@
   <!-- Please keep this list alphabetical. -->
 </ul>
 
-<p><strong>Note:</strong> <em>English (<code>en</code>)</em> 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 original
-  documents written in other languages translated into English. It is best
-  to notify the team coordinator of your language that you volunteer,
-  because we always contact them first. 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>
+<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 
+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>
 </div>
+
 <!--#include virtual="/server/footer.html" --> 
+
 <div id="footer">
 <p>Please send FSF &amp; GNU inquiries to <a
 href="mailto:address@hidden";>&lt;address@hidden&gt;</a>. There are also <a
@@ -437,7 +450,7 @@
 
 <p>Updated: 
 <!-- timestamp start -->
-$Date: 2011/12/19 18:11:17 $
+$Date: 2011/12/27 14:16:28 $
 <!-- timestamp end --></p>
 </div>
 </div>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]