[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/server/standards README.translations.html
|
From: |
Dora Scilipoti |
|
Subject: |
www/server/standards README.translations.html |
|
Date: |
Fri, 30 Dec 2011 12:18:30 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: Dora Scilipoti <dora> 11/12/30 12:18:30
Modified files:
server/standards: README.translations.html
Log message:
Apply modifications.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.translations.html?cvsroot=www&r1=1.190&r2=1.191
Patches:
Index: README.translations.html
===================================================================
RCS file: /web/www/www/server/standards/README.translations.html,v
retrieving revision 1.190
retrieving revision 1.191
diff -u -b -r1.190 -r1.191
--- README.translations.html 30 Dec 2011 06:11:28 -0000 1.190
+++ README.translations.html 30 Dec 2011 12:18:24 -0000 1.191
@@ -76,10 +76,11 @@
system of 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,
+ methods. If you don't get an answer in two weeks,
write to the Translations Manager <a
href="mailto:address@hidden";><address@hidden></a>.
</dd>
+
<dt>As an Occasional Contributor</dt>
<dd>If you just want to submit a new translation and are not
@@ -90,13 +91,14 @@
Manager <a
href="mailto:address@hidden";><address@hidden></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";><address@hidden></a>.
+ <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>
</dd>
-
</dl>
<h3 id="general-guide">General Guide for Translations</h3>
@@ -110,7 +112,7 @@
Project and the specific terminology used in gnu.org:</p>
<ul>
- <li><p>“Copyleft” is a term that can be difficult to
+ <li><p><strong>Copyleft</strong>. This is a term that can be difficult to
translate in some languages. It is a pun on the word
“Copyright” based on the two meanings of
“right”: ethical and directional. You can read the
@@ -120,11 +122,37 @@
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 “Free Software”</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>
+ <li><p><strong>Free Software</strong>. See the <a
+ href="/philosophy/fs-translations.html">Translations
+ of the Term “Free Software”</a> in several languages.</p>
+ </li>
+
+ <li><p><strong>Digital Restrictions Management (DRM)</strong>. This is what
+ we use in gnu.org to avoid the propaganda term “Digital Rights
+ Management”. It means that digital techniques are used to impose
+ restrictions on the user, and these restrictions apply not only to
+ digital but also to physical objects.</p>
+
+ <p>The English term "Digital Restrictions Management" may refer to
+ both:</p>
+
+ <p>1. <strong>Digital Management of Restrictions</strong> <br />
+ 2. Management of Digital Restrictions</p>
+
+ <p>The correct meaning is the first one. Translations should make this
+ clear. In many languages these require different wording. Likewise with
+ “rights” instead of “restrictions”.</p>
+ </li>
+
+ <li><p>When translating “GNU's Not Unix”, please ensure that
+ the translation remains recursive. If a recursive translation cannot be
+ conceived, use the following format (this is an example for Swedish):
+ “GNU's Not Unix (<span xml:lang="sv" lang="sv">
+ GNU är inte Unix</span>)”.</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
@@ -136,26 +164,12 @@
Source Misses the Point of Free Software</a></li>
</ul>
</li>
- <li><p>When translating “GNU's Not Unix”, please ensure
- that the translation remains recursive. If a recursive translation
- cannot be conceived, use the following format (this is an example
- for Swedish): “GNU's Not Unix (<span xml:lang="sv" lang="sv">
- GNU är inte Unix</span>)”.</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
-translated in all available languages, but you should first browse our
+<p>All essays and articles in the following directories should be translated
+in all available languages, but you should first browse our
<a href="/server/standards/translations/priorities.html">Web Translation
Priorities</a>:</p>
@@ -167,82 +181,99 @@
<li><code>philosophy/</code></li>
</ul>
-<p>Again, please coordinate with your language team before starting any
-work, to get clear instructions on how to proceed and to avoid
-duplicating efforts.</p>
+<p>Again, please coordinate with your language team before starting any 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>
+<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>
+
+<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>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";><address@hidden></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.</p>
+<p>The following is an explanation of what a Team Coordinator does
+specifically. In addition to what has already been described, a Team
+Coordinator:</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>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;</p></li>
+
+ <li><p>understands thoroughly how our translation system works, and
+ knows how to use the tools that we have adopted. In the following section
+ we explain briefly how it is done.</p></li>
</ul>
-<h4 id="tools">Tools to Help Translators</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. 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>
-
-<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 “<em><code>make report TEAM=LANG</code></em>”
-if you have <a href="/software/gnun/">GNUN</a> installed.</p>
+<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>A coordinator should also read and be well acquainted with the
- following documentation:</li>
+ <li><p>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.</p></li>
+
+ <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.</p></li>
+
+ <li><p>.po files can be edited by using any .po file editor.</p>
</ul>
+
+<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. You may also
+use “<em><code>make report TEAM=LANG</code></em>” if you
+have GNUN installed.</p>
+
+<h4 id="coord-manuals">Coordinators Manuals</h4>
+
+<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:</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>
+ 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>
+ 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 href="mailto:address@hidden";><address@hidden></a>
-for further assistance.</p>
+<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";><address@hidden></a>
+of your decision. Start reading at least the first two manuals and ask
+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>
@@ -250,14 +281,9 @@
<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 href="mailto:address@hidden";><address@hidden></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>
-
-<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>
+<p>In the following list, the language code is followed by the name of the
+language, and by the name of the Team Coordinator.</p>
+
<ul>
<!-- Please keep this list alphabetical-->
@@ -360,7 +386,8 @@
<li><code>nl</code> -
<a href="https://savannah.gnu.org/projects/www-nl";>Dutch</a>
- (<a href="https://savannah.gnu.org/users/tuijldert";>Tom Uijldert</a>)</li>
+ (<a href="https://savannah.gnu.org/users/tuijldert";>Tom Uijldert</a>)
+ </li>
<li><code>nn</code> - Norwegian Nynorsk
(<a href="https://savannah.gnu.org/users/att";>Andreas Tolfsen</a>,
@@ -421,7 +448,8 @@
<li><code>uk</code> -
<a href="https://savannah.gnu.org/projects/www-uk";>Ukrainian</a>
- (<a href="https://savannah.nongnu.org/users/sudyr";>Evgeniy Sudyr</a>)</li>
+ (<a href="https://savannah.nongnu.org/users/sudyr";>Evgeniy Sudyr</a>)
+ </li>
<li><code>zh-cn</code> -
<a href="https://savannah.gnu.org/projects/www-zh-cn";>Simplified
@@ -443,16 +471,15 @@
<!-- 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";><address@hidden>
- </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 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";><address@hidden></a>.
+</p>
</div>
@@ -465,7 +492,8 @@
There are also <a href="/contact/">other ways to contact</a>
the FSF.<br />
Please send broken links and other corrections or suggestions to
-<a href="mailto:address@hidden";><address@hidden></a>.</p>
+<a href="mailto:address@hidden";><address@hidden></a>.
+</p>
<p>Please see the <a
href="/server/standards/README.translations.html">Translations
@@ -480,7 +508,7 @@
<p>Updated:
<!-- timestamp start -->
-$Date: 2011/12/30 06:11:28 $
+$Date: 2011/12/30 12:18:24 $
<!-- timestamp end -->
</p>
</div>