www-commits
[Top][All Lists]
Advanced
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/server/standards po/README.translations.tra...

From: GNUN
Subject: www/server/standards po/README.translations.tra...
Date: Sat, 11 Aug 2018 17:58:50 -0400 (EDT) 
CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     18/08/11 17:58:50

Modified files:
        server/standards/po: README.translations.translist 
Added files:
        server/standards: README.translations.zh-cn.html 
        server/standards/po: README.translations.zh-cn-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.translations.zh-cn.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/po/README.translations.translist?cvsroot=www&r1=1.23&r2=1.24
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/po/README.translations.zh-cn-en.html?cvsroot=www&rev=1.1

Patches:
Index: po/README.translations.translist
===================================================================
RCS file: /web/www/www/server/standards/po/README.translations.translist,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- po/README.translations.translist    28 Feb 2017 16:59:17 -0000      1.23
+++ po/README.translations.translist    11 Aug 2018 21:58:49 -0000      1.24
@@ -9,6 +9,7 @@
 <span dir="ltr"><a lang="ja" hreflang="ja" 
href="/server/standards/README.translations.ja.html">日本語</a>&nbsp;[ja]</span>
 &nbsp;
 <span dir="ltr"><a lang="pt-br" hreflang="pt-br" 
href="/server/standards/README.translations.pt-br.html">português&nbsp;do&nbsp;Brasil</a>&nbsp;[pt-br]</span>
 &nbsp;
 <span dir="ltr"><a lang="sq" hreflang="sq" 
href="/server/standards/README.translations.sq.html">Shqip</a>&nbsp;[sq]</span> 
&nbsp;
+<span dir="ltr"><a lang="zh-cn" hreflang="zh-cn" 
href="/server/standards/README.translations.zh-cn.html">简体中文</a>&nbsp;[zh-cn]</span>
 &nbsp;
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" 
href="/server/standards/README.translations.html" hreflang="x-default" />
@@ -19,4 +20,5 @@
 <link rel="alternate" type="text/html" lang="ja" hreflang="ja" 
href="/server/standards/README.translations.ja.html" title="日本語" />
 <link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br" 
href="/server/standards/README.translations.pt-br.html" title="português do 
Brasil" />
 <link rel="alternate" type="text/html" lang="sq" hreflang="sq" 
href="/server/standards/README.translations.sq.html" title="Shqip" />
+<link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn" 
href="/server/standards/README.translations.zh-cn.html" title="简体中文" />
 <!-- end translist file -->

Index: README.translations.zh-cn.html
===================================================================
RCS file: README.translations.zh-cn.html
diff -N README.translations.zh-cn.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ README.translations.zh-cn.html      11 Aug 2018 21:58:49 -0000      1.1
@@ -0,0 +1,513 @@
+<!--#set var="ENGLISH_PAGE" 
value="/server/standards/README.translations.en.html" -->
+
+<!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.84 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>www.gnu.org 网页翻译指南 - GNU工程 - 
自由软件基金会</title>
+
+<!--#include virtual="/server/standards/po/README.translations.translist" -->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<h2 id="guide" class="section">www.gnu.org 网页翻译指南</h2>
+
+<h3 id="intro">简介</h3>
+
+<p>翻译 gun.org
+和其上众多文章
以及保持译文的更新是一项需要细致组织的复杂工作。译者
们按语言分成对应的小组，一般每个小组都有一个协调员。然而有些语言还没有相应的小组，同时也有小组缺少协调员。</p>
+
+<p>小组协调员使用软件工具高效地局部更新页面。由 GNU 
现任翻译管理员 Yavor Doganov 专门开发的 <strong>GNUnited
+Nations</strong> (GNUN) 是工å…
·ä¹‹ä¸€ï¼Œå®ƒä½¿è·Ÿè¸ªå’Œç»´æŠ¤éœ€è¦æ›´æ–°çš„译文变得非常容易。</p>
+
+<p>翻译管理员管理小组的整体组织，他通常参与新协调员的培训。</p>
+
+<p>作为小组的一员，您即使完全不了解 GNUN 
也可以为翻译作出贡献，但如果会使用 
GNUN，您可以在更多层面上提供帮助。</p>
+
+<h3 id="who">谁能帮助</h3>
+
+<p>所有的小组总是在寻找新的志愿者
。基本上，在翻译过程中每个人都有这æ 
·ä¸€é¡¹ä»»åŠ¡ï¼šæˆ‘们需要具备良好语言技能的人，以及å…
·å¤‡æˆ–愿意学习技术性技能的人。</p>
+
+<ul>
+  
<li><p>如果您对书面英语有较深的理解，并且很好地掌握了母语，那么您æ—
 ç–‘可以参与翻译或审校。书面英语好并不是必须的。</p></li>
+  <li><p>如果您对英语理解得不太好或完å…
¨ä¸æ‡‚，但熟练掌握了您的母语，那么您可以审阅
别人的译文以确保它们有良好的可读性和行文风格。</p></li>
+  <li><p>如果您是英语母语者
，并且能看懂另外一种语言（看得不快或有点困难也无
所谓），那么您可以帮助改进这种语言的翻译。译者
有时候会误解英语中的习语或表述，然后写下å…
·æœ‰è¯¯å¯¼æ€§ç”šè‡³ä¸æ­£ç¡®çš„文字。而这些错误对于英语母语者
是显而易见的——您可以指出可能的错误并解释正确的意思，这æ
 ·è¯‘者就能正确地重新翻译了。</p></li>
+  
<li><p>如果您倾向于或愿意选择翻译进程中更偏向于技术的方面，您将可以在更大程度上提供帮助；比如准备译文的发布。</p></li>
+</ul>
+
+<h3 id="how">如何参与</h3>
+
+<dl>
+  <dt>作为小组成员</dt>
+    <dd>请阅读下面的<a
+href="#general-guide">通用翻译指南</a>，然后联系相å…
³çš„翻译小组。每个小组都有自己的一套组织工作体系。所以，为了åŠ
 å…
¥ä¸€ä¸ªçŽ°æœ‰çš„小组，您需要从那个小组中了解一些细节。该小组的协调员将会指导您他们特定的方法。如果两周å†
…得不到答复，请联系翻译管理员
+<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。
+    </dd>
+
+  <dt>作为临时贡献者</dt>
+
+    <dd>如果您仅仅想提交一篇新翻译但对长期合作没å…
´è¶£ï¼Œé‚£ä¹ˆè¯·éµç…§ä¸‹é¢çš„<a
+href="#general-guide">通用翻译指南</a>，然后将译文发给对应的<a
+href="#teams">小组协调员</a>（如果有）或翻译管理员<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>（如果没有相应语言的小组或协调员）。</dd>
+
+  <dt>作为小组协调员</dt>
+    
<dd>如果您的语言小组尚未成立或需要一个新协调员，我们会很乐意交由您来æ‹
…任这项任务。作为一名协调员，您需要遵守下面的<a
+href="#general-guide">通用翻译指南</a>以及<a 
href="#coordinator-guide">小组协调员指南</a>。
+      </dd>
+</dl>
+
+<h3 id="general-guide">通用翻译指南</h3>
+
+<p>以下是我们翻译页面的特定目标</p>
+
+<h4 id="clarity">清晰易懂</h4>
+
+<p>除了少数例外，我们翻译的页面是面向大众的。在工作前，请看着原文，问问自己这面向的是程序员还是大众。然后您的工作应针对目æ
 ‡è¯»è€…。</p>
+
+<p>在面向大众的页面中，请避免使用无法在常用词å…
¸æŸ¥åˆ°çš„词语，除了我们的特定说法如 “GNU” 和 
“copyleft”（参见下表）。</p>
+
+<h4 id="accuracy">精确</h4>
+
+<p>为了提供一篇精确且忠于原文的译文，您需要熟悉 GNU 
工程的基本思想和 gun.org 中使用的特定术语。
+</p>
+
+<p>
+请学习<a href="/philosophy"> GNU 工程的哲学 </a>，以便恰当而清
晰地表述它们。下列文章会对您起到很大帮助：
+</p>
+
+<ul>
+  <li><a 
href="/philosophy/free-sw.zh-cn.html">什么是自由软件？</a></li>
+  <li><a 
href="/philosophy/categories.html">自由软件与非自由软件的类别</a></li>
+
+  <li><a href="/philosophy/words-to-avoid.html">应避免的词汇</a></li>
+  <li><a href="/gnu/why-gnu-linux.html">名字里应该有什么</a></li>
+  <li><a
+href="/philosophy/open-source-misses-the-point.zh-cn.html">为什么开源误导了自由软件的重点</a></li>
+</ul>
+
+<p>
+以下列出的概念和内容需要特别处理
+</p>
+
+<ul>
+  
<li><p><strong>Copyleft</strong>。这是一个在一些语言中难以翻译的词语。这是å
…³äºŽâ€œCopyright”（“版权”）的双å…
³è¯­â€”—基于“right”的两种含义：关于伦理的（权利）和å…
³äºŽæ–¹å‘的（右）。您可以阅读<a
+href="/copyleft/copyleft.html">什么是 Copyleft？</a>
+来了解更多信息以及如何译成别的语言。您会看到在多数情
况下它根本无
法翻译，所以如果您找不到一个好的译名，唯一的选择可能是直接使用英语单词。</p></li>
+
+  <li><p><strong>Free 
Software（自由软件）</strong>。大多数的语言有意为“自由”的词语以及另一个意为“å
…è´¹â€çš„词语。在
+gnu.org
+上，我们用“&ldquo;free&rdquo;”时一般指代自由，而表示å…
è´¹åˆ™ç”¨â€œ&ldquo;gratis&rdquo;”。因此，请以“自由”而不是“å…
è´¹â€æ¥ç¿»è¯‘“&ldquo;free&rdquo;”。</p>
+
+    <p>然而，在一些旧的页面比如 GNU
+宣言和初始声明里，我们还没有将å…
¶åŒºåˆ†ã€‚在翻译这些页面时，您可能需要对每个出现的“free”仔细考虑。您可以选择保留英语单词，紧接着解释它在那次出现时的含义：自由，还是å
…è´¹ï¼Œè¿˜æ˜¯æ¨¡ç³Šåœ°ä¸¤è€…都有。</p>
+
+    <p>不过，即使在这些旧的页面里，“free 
software”里的“free”一般意为“自由”</p>
+
+    <p>各种语言中对“Free Software”的翻译参见<a
+href="/philosophy/fs-translations.zh-cn.html">“自由软件”一词的翻译</a>。</p>
+  </li>
+
+  <li><p><strong>Digital Restriction Management 
(DRM)（数字限制管理）</strong>。我们在 gun.org
+里用这个短语来避免鼓吹性的“Rigital Rights
+Management”（“数字版权管理”）。它的意思是数字技术被用于向用户施åŠ
 å¼ºåˆ¶é™åˆ¶ï¼Œå¹¶ä¸”这些限制不仅用于数码，还用于实物。</p> 
+
+    <p>不过，英语短语“Right Restrictions 
Management”有一点小小的歧义，它可理解为以下两种意思：</p>
+
+    <ol>
+      <li> <strong>限制的数字化管理</strong>。</li>
+      <li> 数字限制的管理。</li>
+    </ol>
+
+    
<p>在许多语言里，这两种意义的表述是不同的。正确的意义是前è€
…，所以译者应使å…
¶æ˜Žç¡®ï¼Œå¹¶ä¸”以“限制”（restrictions）代替“版权”（right）。</p>
+  </li>
+
+  <li>
+    <p><strong>Should</strong>。在有å…
³ä¼¦ç†çš„问题上，“should”意为别的做法都是错误的。比如《为什么软件应该是自由的》解释了为什么在我们生活的世界里让软件非自由是错误的。</p>
+
+    
<p>所以，请用表达强烈道德义务的动词形式来翻译“should”。不要译成这æ
 
·çš„意思“软件最好是自由，在理想世界中软件会是自由的”。这不够强烈。</p>
+  </li>
+
+  <li><p><strong>GNU's Not Unix</strong>。当翻译“GNU's Not
+Unix”时，请确保译文仍然保持递归形式。如果找不到递归形式的译文，就使用以下的形式（这里以西班牙语为例）：“GNU's
 Not Unix (<span
+xml:lang="sv" lang="sv"> GNU &auml;r inte Unix</span>)”</p></li>
+   
+  <li><p>例外：页面 philosophy/words-to-avoid.html
+是对于我们选用术语原则的一个例外，因
为它写的是<em>不该</em>说的话的例子。比如，我们一般避å…
è¯ç»„“数字版权管理”（“Digital Rights
+Management”）。但是我们在该页面提到了这个词组以建议å…
¶ä»–人避免使用它。</p>
+
+    <p>作为译者，最好遵循英文原文。在原文写着“Digital 
Rights Management”的地方，按ç…
§åŽŸæ–‡æ¥ç¿»è¯‘；在原文写着“Digital
+Restrictions Management”的地方，也按照原文来翻译。</p></li>
+
+  
<li><p><strong>Surveillance</strong>。这个单词在罗曼语族的语言中有同形异义词，原å›
 åœ¨äºŽå®ƒçš„拉丁词æ 
¹ã€‚在英语中，它特别地表示对涉嫌干坏事的个人或组织的严密观察；这会使个人或组织不安å
…
¨ã€‚在另一方面，在一些罗曼语族的语言（如法语）中，该词的同形异义词被更宽泛地使用；它可能描述牧羊人对他的羊或老师对å
…¶å­¦ç”Ÿè¿™ç±»å–„意的看护。</p>
+
+    
<p>当翻译该词时，请确保您的用语不会被理解为“善意的看护”，如果没有专门的表述，在专有软件的语境下，意为“监视”（“spying”）的用语可能会是符合要求的。</p></li>
+</ul>
+
+<p>更多内容参见 <a
+href="/server/standards/translations/interpreters-guide.html">Interpreters
+Guide</a>。</p>
+
+<p>在将您的译文安装至 gun.org 或为此提交译文前：</p>
+
+<ul>
+  
<li>让您的译文被您所在的小组中尽可能多的成员审查。同侪审查对翻译的质量至å
…³é‡è¦ã€‚太多错误（尤其是明显的错误）在译者审阅
自己的译文时被漏掉了。进行同侪审查的一个通常的做法是将译文发到小组的邮件列表：成员们恰当的引用特定部分，发表评论。结果是更好的译文质量，å›
 ä¸ºæœ‰æ›´å¤šçš„人看过它。</li>
+
+  
<li>如果您的语言的小组还没有成立，给您那些不了解自由软件或
 GNU 的朋友看您的译文，看看他们能否清晰地理解。</li>
+</ul>
+
+<h4 id="licensing">译文的许可证</h4>
+
+<p>译文应使用与原文相同的许可证。如果原文带着一份知识å
…
±äº«ç½²åè®¸å¯ï¼Œé‚£ä¹ˆè¯·ä½¿ç”¨ç›¸åŒçš„许可证，如果原文说它是在å
…¬å…±é¢†åŸŸçš„，译文也应该这么说。</p>
+
+<p>特殊规则参见在 <cite>GNU Web Translators Manual</cite> 中的 <a
+href="/software/trans-coord/manual/web-trans/html_node/Distribution-Terms.html">Distribution
+Terms</a></p>
+
+<h4 id="what">翻译什么</h4>
+
+<p>所有在以下目录的文章
都应翻译成所有可用的语言，但您应该先浏览我们的<a
+href="/server/standards/translations/priorities.html">优å…
ˆç¿»è¯‘页面</a>：</p>
+
+<ul>
+  <li><code>education/</code></li>
+  <li><code>gnu/</code></li>
+  <li><code>licenses/</code></li>
+  <li><code>philosophy/</code></li>
+</ul>
+
+<p>再次说明，请在开始任何工作前与您的语言的小组协调，以得到å
…³äºŽå¦‚何工作及避免重复劳动的清晰介绍。
+</p>
+
+<p><em><strong>注：</strong></em><code>software/</code> 
目录里的材料是属于个别 GNU
+软件包的。如果您想翻译这个目录的东西，请与相应软件包
的维护者交谈以了解他们想做什么。</p>
+
+<h4 id="translators-manual">译者手册</h4>
+
+<p>您可能要阅读 <a href="/software/trans-coord/manual/web-trans/">GNU 
Web Tranlators
+Manual</a>，如果希望对我们翻译系统如何工作有更好的理解。但请å
…ˆå’Œå°ç»„交流；最有可能的是您不需要阅读这篇文档。</p>
+
+<h3 id="coordinator-guide">小组协调员指南</h3>
+
+<p>以下解释小组协调员所做的特殊事情
。除了以上已经描述过的事情，小组协调员还需要：</p>
+
+<ul>
+  <li><p>保证所有发布的文本忠
于原文，并且尊重我们网站使用的术语。所有被小组成员或临时贡献è€
…提交的译文应在被发布之前由小组协调员审阅
并批准。</p></li>
+
+  
<li><p>理解透彻我们的翻译系统是如何工作的，以及知道如何使用我们采用的工å
…·ã€‚下文我们会简要说明怎么做。</p></li>
+</ul>
+
+<h4 id="tools">工具</h4>
+
+<p>我们使用 .po (Portable Object) 文件来处理和维护译文。.po 
文件包含原文和译文，划分成段落。以下是我们的做法：</p>
+
+<ul>
+  <li><p>当一篇新文章
发布在我们的网站时，我们一开始提到的程序 GNUN 
会基于该文章生成一个 .pot (.po 模板) 文件。这个 .pot 
文件被重命名为
+.po 以进行翻译。一经翻译，这个 .po 文件就会被提交。然后 
GNUN 就会检查，如果代码中没有错误，译文的 HTML 
版本会被自动地提交到网站上。</p></li>
+
+  <li><p>任何时候如果原始的 HTML 文章发生了改变，.pot 和 .po 
文件就会被 GNUN 重新生成以融合更改,清
晰显示改变了的文本。然后译者只需要在
+.po 文件里更新那一部分。当提交了更新的 .po 文件，译文的 
HTML 版本就会自动在网站里更新。</p></li>
+
+  <li><p>.po 文件可以用任何的 .po 文件编辑器编辑。</p>
+
+      <p>注：有些小组成员或临时贡献者可能会发现用 .po 
文件来翻译是困难或不便的。然而，不应该拒绝以纯文本提交的贡献。为了鼓励使用
 PO
+文件，协调员可以向那些贡献者提供针对缺乏计算机技能者
的简单指导。</p></li>
+</ul>
+
+<p>我们还实现了通知工具以向译者通知原文的更改。任何情
况下，一个小组协调员需要订阅我们的 <a
+href="http://lists.gnu.org/mailman/listinfo/www-commits";>www-commits</a>
+邮件列表以留心更改的页面。如果安装了 
GNUN，您也可能使用 “<em><code>make report
+TEAM=LANG</code></em>”。</p>
+
+<h4 id="coord-manuals">协调员手册</h4>
+
+<p>下面列出的手册详细地解释了上文中我们简要介绍的翻译过程。协调员有å¿
…要阅读并熟悉它们。</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="/server/standards/README.webmastering.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>
+</ul>
+
+<p>在您阅
读了这整个页面后，如果您打算进行志愿活动并被列为您的语言的小组协调员，请将您的决定告知翻译管理员
 <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。开始阅
读至少前两个手册，并且如果有任何疑问，向翻译管理员寻求帮助。</p>
+
+<h3 id="teams">翻译小组</h3>
+<!--Some docs refer to this anchor-->
+<span id="TranslationsUnderway"></span> 
+
+<p>建立新小组的志愿者不仅会受到欢迎，而且还可以在学习
过程中得到帮助。</p>
+
+<p>以下的列表中，语言代ç 
è·Ÿéšç€è¯­è¨€çš„名字，接着就是小组协调员的名字。</p>
+
+<ul>
+
+<!-- Please keep this list alphabetical-->
+<li><code>ar</code> - <a
+href="https://savannah.nongnu.org/projects/www-ar";>Arabic</a> (<a
+href="https://savannah.gnu.org/users/ka2in";>Fayçal Alami</a> - New
+coordinator needed) </li>
+
+  <li><code>az</code> - Azerbaijani (<a
+href="https://savannah.gnu.org/users/igrar";>Igrar Huseynov</a> - New
+coordinator needed) </li>
+    
+  <li><code>bg</code> - <a
+href="https://savannah.gnu.org/projects/www-bg";>Bulgarian</a> (<a
+href="https://savannah.gnu.org/users/yavor";>Yavor Doganov</a> - New
+coordinator needed)</li>
+ 
+  <li><code>bn</code> - <a
+href="https://savannah.gnu.org/projects/www-bn";>Bengali</a> (<a
+href="https://savannah.gnu.org/users/suzan";>Khandakar Mujahidul Islam</a> -
+New coordinator needed) </li>
+    
+  <li><code>ca</code> - <a
+href="https://savannah.gnu.org/projects/www-ca";>Catalan</a> (<a
+href="https://savannah.gnu.org/users/puigpe";>Miquel Puigpelat</a>) </li>
+
+  <li><code>cs</code> - <a
+href="https://savannah.gnu.org/projects/www-cs";>Czech</a> (<a
+href="https://savannah.gnu.org/users/franta";>František Kučera</a>)</li>
+    
+  <li><code>da</code> - <a
+href="https://savannah.gnu.org/projects/www-da";>Danish</a> (<a
+href="https://savannah.gnu.org/users/erikg";>Erik Gravgaard</a> - New
+coordinator needed) </li>
+
+  <li><code>de</code> - <a
+href="https://savannah.gnu.org/projects/www-de";>German</a> (<a
+href="https://savannah.gnu.org/users/joeko";>Joerg Kohne</a>)</li>
+  
+  <li><code>el</code> - <a
+href="https://savannah.gnu.org/projects/www-el";>Greek</a> (<a
+href="https://savannah.gnu.org/users/gzarkadas";>Georgios Zarkadas</a>) </li>
+
+  <li><code>eo</code> - <a
+href="https://savannah.gnu.org/projects/www-eo";>Esperanto</a> (<a
+href="https://savannah.gnu.org/users/civodul";>Ludovic Court&egrave;s</a> -
+New coordinator needed) </li>
+    
+  <li><code>es</code> - <a
+href="https://savannah.gnu.org/projects/www-es";>Spanish</a> (<a
+href="https://savannah.gnu.org/users/dora";>Dora Scilipoti</a>, <a
+href="https://savannah.gnu.org/users/jfrtnaga";>Javier Fernández
+Retenaga</a>)</li>
+
+  <li><code>fa</code> - <a
+href="https://savannah.gnu.org/projects/www-fa";>Farsi/Persian</a> (<a
+href="https://savannah.gnu.org/users/esmaeeli";>Abbas Esmaeeli
+Some&lsquo;eh</a>) </li>
+    
+  <li><code>fi</code> - <a
+href="https://savannah.gnu.org/projects/www-fi";>Finnish</a> (<a
+href="https://savannah.gnu.org/users/solarius";>Ville</a> - New coordinator
+needed)</li>
+
+  <li><code>fr</code> - <a
+href="https://savannah.gnu.org/projects/www-fr";>French</a> (<a
+href="https://savannah.gnu.org/users/barbier";>Denis Barbier</a>, <a
+href="https://savannah.gnu.org/users/th_g";>Thérèse Godefroy</a>)</li>
+    
+  <li><code>he</code> - <a
+href="https://savannah.gnu.org/projects/www-he";>Hebrew</a> (New coordinator
+needed) </li>
+
+  <li><code>hr</code> - <a
+href="https://savannah.gnu.org/projects/www-hr";>Croatian</a> (<a
+href="https://savannah.gnu.org/users/mist";>Martina Bebek</a> - New
+coordinator needed)</li>
+
+  <li><code>id</code> - <a
+href="https://savannah.gnu.org/projects/www-id";>Indonesian</a> (New
+coordinator needed) </li>
+    
+  <li><code>it</code> - <a
+href="https://savannah.gnu.org/projects/www-it";>Italian</a> (<a
+href="https://savannah.gnu.org/users/pescetti";>Andrea Pescetti</a>) </li>
+
+  <li><code>ja</code> - <a
+href="https://savannah.gnu.org/projects/www-ja";>Japanese</a> (<a
+href="https://savannah.gnu.org/users/gniibe";>NIIBE Yutaka</a>)</li>
+    
+  <li><code>ko</code> - <a
+href="https://savannah.gnu.org/projects/www-ko";>Korean</a> (<a
+href="https://savannah.gnu.org/users/blueguy";>Jongmin Yoon</a>) </li>
+
+  <li><code>ku</code> - <a
+href="https://savannah.gnu.org/projects/www-ku";>Kurdish</a> (New coordinator
+needed) </li>
+    
+  <li><code>ml</code> - <a
+href="https://savannah.gnu.org/projects/www-ml";>Malayalam</a> (New
+coordinator needed) </li>
+    
+  <li><code>nb</code> - <a
+href="https://savannah.gnu.org/projects/www-nb";>Norwegian Bokm&aring;l</a>
+(<a href="https://savannah.gnu.org/users/att";> Andreas Tolfsen</a> - New
+coordinator needed) </li>
+   
+  <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>, <a
+href="https://savannah.gnu.org/users/jvs";>Justin van Steijn</a>)
+  </li>
+    
+  <li><code>nn</code> - Norwegian Nynorsk (<a
+href="https://savannah.gnu.org/users/att";>Andreas Tolfsen</a> - New
+coordinator needed) </li>
+
+  <li><code>pl</code> - <a
+href="https://savannah.gnu.org/projects/www-pl";>Polish</a> (<a
+href="https://savannah.gnu.org/users/jsowoc";>Jan Owoc</a>) </li>
+    
+  <li><code>pt-br</code> - <a
+href="https://savannah.gnu.org/projects/www-pt-br";>Brazilian Portuguese</a>
+(<a href="https://savannah.gnu.org/users/rafaelff1";>Rafael Fontenelle</a>) 
</li>
+
+  <li><code>ro</code> - <a
+href="https://savannah.gnu.org/projects/www-ro";>Romanian</a> (<a
+href="https://savannah.gnu.org/users/tct";>Tiberiu C.  Turbureanu</a> - New
+coordinator needed) </li>
+  
+  <li><code>ru</code> - <a
+href="https://savannah.nongnu.org/projects/www-ru";>Russian</a> (<a
+href="https://savannah.gnu.org/users/jimcrow";>Anatoly A.  Kazantsev</a>, <a
+href="https://savannah.gnu.org/users/ineiev";>Pavel Kharitonov</a>) </li>
+
+  <li><code>sk</code> - <a
+href="https://savannah.nongnu.org/projects/www-sk";>Slovak</a> (<a
+href="https://savannah.gnu.org/users/dominiks";>Dominik Smatana</a> - New
+coordinator needed) </li>
+    
+  <li><code>sq</code> - <a
+href="https://savannah.gnu.org/projects/www-sq";>Albanian</a> (<a
+href="https://savannah.gnu.org/users/beso";>Besnik Bleta</a>)</li>
+
+  <li><code>sr</code> - <a
+href="https://savannah.gnu.org/projects/www-sr";>Serbian</a> (<a
+href="https://savannah.gnu.org/users/Ctpajgep";>Strahinya Radich</a>) </li>
+  
+  <li><code>ta</code> - <a
+href="https://savannah.gnu.org/projects/www-ta";>Tamil</a> (<a
+href="https://savannah.gnu.org/users/amachutechie";>Sri Ramadoss</a> - New
+coordinator needed) </li>
+
+  <li><code>th</code> - <a
+href="https://savannah.gnu.org/projects/www-th";>Thai</a> (New coordinator
+needed) </li>
+    
+  <li><code>tl</code> - <a
+href="https://savannah.gnu.org/projects/www-tl";>Tagalog</a> (New coordinator
+needed) </li>
+    
+  <li><code>tr</code> - <a
+href="https://savannah.gnu.org/projects/www-tr";>Turkish</a> (<a
+href="https://savannah.gnu.org/users/exalted";>Ali Servet D&ouml;nmez</a> -
+New coordinator needed) </li>
+
+  <li><code>uk</code> - <a
+href="https://savannah.gnu.org/projects/www-uk";>Ukrainian</a> (<a
+href="https://savannah.gnu.org/users/andriykopanytsia";>Andriy Bandura</a>)</li>
+    
+  <li><code>zh-cn</code> - <a
+href="https://savannah.gnu.org/projects/www-zh-cn";>简体中文</a> (<a
+href="https://savannah.gnu.org/users/wxie";> Xie Wensheng</a>) </li>
+
+  <li><code>zh-tw</code> - <a
+href="https://savannah.gnu.org/projects/www-zh-tw";>繁体中文</a> (<a
+href="https://savannah.gnu.org/users/zerngjia";> Cheng-Chia Tseng</a>) </li>
+  
+  <li><code>??</code> - Not available? Then this line is reserved for you.</li>
+
+<!-- Please keep this list alphabetical. -->
+</ul>
+
+<p>注：英语（en）是一个特殊的例子。这个站点上大部分的å†
…容都是英语写的，英语是 GNU
+工程的事实上的语言。我们<em>偶尔</em>需要将非英语文档翻译成英语的。最好就是告知您的语言的小组协调员如果您想参åŠ
 å¿—愿活动。如果没有小组协调员并且您想起到帮助，请联系
+<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。
+</p>
+ 
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.zh-cn.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>请将对FSF&amp;GNU的一般询问发送到<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。还有一些å…
¶ä»–联系FSF的<a
+href="/contact/">方式</a>。关于链接错误和”å…
¶ä»–更正或建议“请发信到<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。</p>
+
+<p>
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+关于协调和提交本文的翻译，请参看<a
+href="/server/standards/README.translations.html">翻译须知</a>。</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 4.0.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+<p>Copyright &copy; 2014, 2015, 2016, 2017 Free Software Foundation, Inc.</p>
+
+<p>本页面使用<a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative Commons
+Attribution-NoDerivatives 4.0 International License</a>授权。</p>
+
+<!--#include virtual="/server/bottom-notes.zh-cn.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<b>翻译</b>：<a href="mailto:address@hidden";>&lt;Hagb
+（郭俊余）&gt;</a>，2018。<br></br>
+<b>翻译团队</b>：<a rel="team"
+href="https://savannah.gnu.org/projects/www-zh-cn/";>&lt;CTT&gt;</a>，2018。</div>
+
+<p class="unprintable"><!-- timestamp start -->
+最后更新：
+
+$Date: 2018/08/11 21:58:49 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: po/README.translations.zh-cn-en.html
===================================================================
RCS file: po/README.translations.zh-cn-en.html
diff -N po/README.translations.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/README.translations.zh-cn-en.html        11 Aug 2018 21:58:49 -0000      
1.1
@@ -0,0 +1,673 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.84 -->
+
+<title>Guide to Translating Web Pages on www.gnu.org 
+- GNU Project - Free  Software Foundation</title>
+
+<!--#include virtual="/server/standards/po/README.translations.translist" -->
+<!--#include virtual="/server/banner.html" -->
+
+<h2 id="guide" class="section">Guide to Translating Web Pages on
+www.gnu.org</h2>
+
+<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>
+
+<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>
+
+<p>The Translations Manager is the person in charge of the overall 
+organization of teams and is generally involved in training new Team 
+Coordinators.</p>
+
+<p>As a Team Member, you can contribute to translations without knowing 
+anything about GNUN, but you can help at more levels if you know how to 
+use it.</p>
+
+<h3 id="who">Who can help</h3>
+
+<p>All teams are always looking for new volunteers. Basically, there is 
+a 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 
+    English idioms and expressions and write translations that are 
+    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>
+</ul>
+
+<h3 id="how">How to Participate</h3>
+
+<dl>
+  <dt>As a Team Member</dt>
+    <dd>Please read the <a href="#general-guide">General Guide for 
+      Translations</a> below and then contact the relevant 
+      <a href="#teams">translation team</a>. Each team has its own 
+      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 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 href="#general-guide">General Guide for Translations</a> below 
+      and then send your translation to the appropriate <a href="#teams">
+      Team 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 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>
+
+<p>Here are our specific goals for our translated pages.</p>
+
+<h4 id="clarity">Clarity</h4>
+
+<p>With few exceptions, the pages we translate are addressed to the
+general public.  Before working on a page, please look at the original
+and ask yourself whether it is addressed to programmers or to the
+general public.  Then aim your translation at the same audience.</p>
+
+<p>In pages meant for the general public, please avoid words that are not
+found in common dictionaries, except for our special terms such as
+&ldquo;GNU&rdquo; and &ldquo;copyleft&rdquo; (see the list below).</p>
+
+<h4 id="accuracy">Accuracy</h4>
+
+<p>In order to produce a translation which is accurate and faithful to
+the original, you need to be familiar with the basic concepts of the
+GNU Project and the specific terminology used in gnu.org.
+</p>
+
+<p>
+Please study the <a href="/philosophy"> philosophy </a> of the free
+software movement, so that you can present it properly and clearly.
+The following articles will be particularly helpful:
+</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 
+    Nonfree Software</a></li>
+
+  <li><a href="/philosophy/words-to-avoid.html">Words to Avoid</a></li>
+  <li><a href="/gnu/why-gnu-linux.html">What's in a Name?</a></li>
+  <li><a href="/philosophy/open-source-misses-the-point.html">Open 
+    Source Misses the Point of Free Software</a></li>
+</ul>
+
+<p>
+These terms and files need special attention:
+</p>
+
+<ul>
+  <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 
+    &ldquo;Copyright&rdquo; based on the two meanings of 
+    &ldquo;right&rdquo;: ethical and directional. You can read the 
+    article <a href="/copyleft/copyleft.html">What is Copyleft?</a> to 
+    learn more about it and see how it has been translated into other 
+    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><strong>Free Software</strong>. Most languages have a word
+    for free-as-in-freedom and another word for gratis (zero price).
+    In gnu.org we generally use &ldquo;free&rdquo; only to refer to
+    freedom, and we say &ldquo;gratis&rdquo; when we mean zero price.
+    Thus, please translate &ldquo;free&rdquo; using the word that
+    means free-as-in-freedom, not the one that refers to price.</p>
+
+    <p>However, in some old pages, such as the GNU Manifesto and the
+    initial announcement, we did not yet make the distinction.  In
+    translating these pages, you may need to think carefully about the
+    proper treatment of each occurrence of the word
+    &ldquo;free&rdquo;.  You might choose to leave the word in
+    English, followed by the explanation of its meaning in that
+    occurrence: either freedom, price, or ambiguously both.</p>
+
+    <p>However, even in these old pages, the word you normally
+    use to translate &ldquo;free&rdquo; in &ldquo;free software&rdquo;
+    should be the one that refers to freedom.</p>
+
+    <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><strong>Digital Restrictions Management (DRM)</strong>. This is what 
+    we use in gnu.org to avoid the propaganda term &ldquo;Digital Rights 
+    Management&rdquo;. 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>However, there is a subtle ambiguity in the English term
+    &ldquo;Digital Restrictions Management&rdquo;.  It can be interpreted in 
two
+    ways:</p>
+
+    <ol>
+      <li> <strong>Digital Management of Restrictions</strong>.</li>
+      <li> Management of Digital Restrictions.</li>
+    </ol>
+
+    <p>In many languages these require different wording. The correct
+    meaning is the first one, so translations should make this clear.
+    Likewise with &ldquo;rights&rdquo; instead of
+    &ldquo;restrictions&rdquo;.</p>
+  </li>
+
+  <li>
+    <p><strong>Should</strong>. In regard to an ethical issue, 
+    &ldquo;should&rdquo; means it would be wrong to do anything else.  For 
+    instance, the page entitled &ldquo;Why Software Should Be Free&rdquo; 
+    explains why it is wrong to make software nonfree in the actual world 
+    we live in.</p>
+
+    <p>Therefore, please translate &ldquo;should&rdquo; using a verb
+    form that implies a strong ethical obligation.  Don't translate it
+    in a way that means &ldquo;it would be preferable for software to
+    be free&rdquo; or &ldquo;in an ideal world, software would be
+    free&rdquo;.  Those are not strong enough.</p>
+  </li>
+
+  <li><p><strong>GNU's Not Unix</strong>. 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): 
+    &ldquo;GNU's Not Unix (<span xml:lang="sv" lang="sv">
+    GNU &auml;r inte Unix</span>)&rdquo;.</p></li>
+   
+  <li><p>Exception: The page philosophy/words-to-avoid.html is an exception 
+    to our usual policies about which terminology to use, because it
+    presents examples of what <em>not</em> to say.  For instance, in
+    general we shun the term &ldquo;Digital Rights Management&rdquo;.
+    However, we cite that term in philosophy/words-to-avoid.html in
+    order to advise others to shun it.</p>
+
+    <p>As a translator, it is best if you follow the English text.
+    Where the English text says &ldquo;Digital Rights
+    Management&rdquo;, translate that.  Where the English text says
+    &ldquo;Digital Restrictions Management&rdquo;, translate
+    that.</p></li>
+
+  <li><p><strong>Surveillance</strong>. This word has false-friends in 
+    Romance languages because of its Latin root. In English, it specifically 
+    means the close observation of a person or organization under 
+    suspicion of wrongdoing; this makes the surveillee unsafe. In some 
+    Romance languages on the other hand (for instance in French), the 
+    false-friend of &ldquo;surveillance&rdquo; is used more widely; it 
+    may describe the benevolent watch of a shepherd over his sheep or of 
+    a teacher over her students.</p>
+
+    <p>When translating &ldquo;surveillance&rdquo;, please make sure you 
+    don't use a word which could be interpreted as &ldquo;benevolent 
+    watch&rdquo;. If there is no specialized term, the word which means 
+    &ldquo;spying&rdquo; may be adequate in the context of proprietary 
+    software.</p></li>
+</ul>
+
+<p>For more info, see <a
+href="/server/standards/translations/interpreters-guide.html">
+Interpreters Guide</a></p>
+
+<p>Before installing or before submitting your translation for 
+installation in gnu.org:</p>
+
+<ul>
+  <li>Have your translation reviewed by as many members of your team as 
+      possible. Peer review is crucial for the quality of the translation 
+      process. Too many errors are just missed (especially if they are 
+      obvious) when the translator does a final review of her own 
+      translation. One common technique to performing such reviews is to 
+      send the translation to the team's mailing list: members comment on
+      specific parts, quoting them appropriately. The result is better 
+      quality of the translation, since more people looked at it.</li>
+
+  <li>If there is no team established for your language, show your 
+      translations to friends who are not experts on free software or GNU, 
+      to see if they understand the translation clearly.</li>
+</ul>
+
+<h4 id="licensing">Licensing of Translations</h4>
+
+<p>A translation page should be licensed just like the original page.
+If the original page carries a Creative Commons license, use the same
+Creative Commons license.  If the original page says it is in the public
+domain, the translation should say the same thing.</p>
+
+<p>For specific rules, see <a
+href="/software/trans-coord/manual/web-trans/html_node/Distribution-Terms.html">
+Distribution Terms</a> in the <cite>GNU Web Translators Manual</cite>.</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 
+<a href="/server/standards/translations/priorities.html">Web Translation 
+Priorities</a>:</p>
+
+<ul>
+  <li><code>education/</code></li>
+  <li><code>gnu/</code></li>
+  <li><code>licenses/</code></li>
+  <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><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>
+
+<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>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><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</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>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>
+
+      <p>Note: Some team members or occasional contributors may find it
+      difficult or inconvenient to translate using PO files. However,
+      contributions submitted as plain text format should not be rejected.
+      To encourage the use of PO files, coordinators can provide those
+      contributors with a simple guide aimed at people with little
+      computer skills. 
+      <a href="/server/standards/translations/po-how-to.html">Here is an 
+      example</a>.</p></li>
+</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 &ldquo;<em><code>make report TEAM=LANG</code></em>&rdquo; 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>
+
+  <li><a href="/server/standards/README.webmastering.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>
+</ul>
+
+<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.</p>
+
+<h3 id="teams">Translation Teams</h3>
+<span id="TranslationsUnderway"><!--Some docs refer to this anchor--></span> 
+
+<p>Volunteers to establish new teams are more than welcome and will be
+assisted during the learning process.</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-->
+  
+  <li><code>ar</code> - 
+    <a href="https://savannah.nongnu.org/projects/www-ar";>Arabic</a> 
+    (<a href="https://savannah.gnu.org/users/ka2in";>Fayçal Alami</a> - 
+    New coordinator needed) </li>
+
+  <li><code>az</code> - Azerbaijani 
+    (<a href="https://savannah.gnu.org/users/igrar";>Igrar Huseynov</a> - 
+    New coordinator needed) </li>
+    
+  <li><code>bg</code> - 
+    <a href="https://savannah.gnu.org/projects/www-bg";>Bulgarian</a> 
+    (<a href="https://savannah.gnu.org/users/yavor";>Yavor Doganov</a> -
+    New coordinator needed)</li>
+ 
+  <li><code>bn</code> - 
+    <a href="https://savannah.gnu.org/projects/www-bn";>Bengali</a> 
+    (<a href="https://savannah.gnu.org/users/suzan";>Khandakar Mujahidul
+    Islam</a> - New coordinator needed) </li>
+    
+  <li><code>ca</code> - 
+    <a href="https://savannah.gnu.org/projects/www-ca";>Catalan</a> 
+    (<a href="https://savannah.gnu.org/users/puigpe";>Miquel 
+    Puigpelat</a>) </li>
+
+  <li><code>cs</code> - 
+    <a href="https://savannah.gnu.org/projects/www-cs";>Czech</a>
+    (<a href="https://savannah.gnu.org/users/franta";>František 
Kučera</a>)</li>
+    
+  <li><code>da</code> - 
+    <a href="https://savannah.gnu.org/projects/www-da";>Danish</a> 
+    (<a href="https://savannah.gnu.org/users/erikg";>Erik Gravgaard</a> - 
+    New coordinator needed) </li>
+
+  <li><code>de</code> - 
+    <a href="https://savannah.gnu.org/projects/www-de";>German</a> 
+    (<a href="https://savannah.gnu.org/users/joeko";>Joerg Kohne</a>)</li>
+  
+  <li><code>el</code> - 
+    <a href="https://savannah.gnu.org/projects/www-el";>Greek</a> 
+    (<a href="https://savannah.gnu.org/users/gzarkadas";>Georgios 
+    Zarkadas</a>) </li>
+
+  <li><code>eo</code> - 
+    <a href="https://savannah.gnu.org/projects/www-eo";>Esperanto</a> 
+    (<a href="https://savannah.gnu.org/users/civodul";>Ludovic 
+    Court&egrave;s</a> - New coordinator needed) </li>
+    
+  <li><code>es</code> - 
+    <a href="https://savannah.gnu.org/projects/www-es";>Spanish</a> 
+    (<a href="https://savannah.gnu.org/users/dora";>Dora Scilipoti</a>,
+    <a href="https://savannah.gnu.org/users/jfrtnaga";>Javier Fernández
+    Retenaga</a>)</li>
+
+  <li><code>fa</code> - 
+    <a href="https://savannah.gnu.org/projects/www-fa";>Farsi/Persian</a> 
+    (<a href="https://savannah.gnu.org/users/esmaeeli";>Abbas Esmaeeli
+    Some&lsquo;eh</a>) </li>
+    
+  <li><code>fi</code> - 
+    <a href="https://savannah.gnu.org/projects/www-fi";>Finnish</a> 
+    (<a href="https://savannah.gnu.org/users/solarius";>Ville</a> - New
+    coordinator needed)</li>
+
+  <li><code>fr</code> - 
+    <a href="https://savannah.gnu.org/projects/www-fr";>French</a> 
+    (<a href="https://savannah.gnu.org/users/barbier";>Denis Barbier</a>,
+     <a href="https://savannah.gnu.org/users/th_g";>Thérèse Godefroy</a>)</li>
+    
+  <li><code>he</code> - 
+    <a href="https://savannah.gnu.org/projects/www-he";>Hebrew</a> (New
+    coordinator needed) </li>
+
+  <li><code>hr</code> - 
+    <a href="https://savannah.gnu.org/projects/www-hr";>Croatian</a> 
+    (<a href="https://savannah.gnu.org/users/mist";>Martina Bebek</a> -
+    New coordinator needed)</li>
+
+  <li><code>id</code> - 
+    <a href="https://savannah.gnu.org/projects/www-id";>Indonesian</a> 
+    (New coordinator needed) </li>
+    
+  <li><code>it</code> - 
+    <a href="https://savannah.gnu.org/projects/www-it";>Italian</a> 
+    (<a href="https://savannah.gnu.org/users/pescetti";>Andrea 
+    Pescetti</a>) </li>
+
+  <li><code>ja</code> - 
+    <a href="https://savannah.gnu.org/projects/www-ja";>Japanese</a> 
+    (<a href="https://savannah.gnu.org/users/gniibe";>NIIBE Yutaka</a>)</li>
+    
+  <li><code>ko</code> -
+    <a href="https://savannah.gnu.org/projects/www-ko";>Korean</a> 
+    (<a href="https://savannah.gnu.org/users/blueguy";>Jongmin Yoon</a>) </li>
+
+  <li><code>ku</code> - 
+    <a href="https://savannah.gnu.org/projects/www-ku";>Kurdish</a> (New 
+    coordinator needed) </li>
+    
+  <li><code>ml</code> - 
+    <a href="https://savannah.gnu.org/projects/www-ml";>Malayalam</a> 
+    (New coordinator needed) </li>
+    
+  <li><code>nb</code> - 
+    <a href="https://savannah.gnu.org/projects/www-nb";>Norwegian 
+    Bokm&aring;l</a> (<a href="https://savannah.gnu.org/users/att";>
+    Andreas Tolfsen</a>
+    - New coordinator needed) </li>
+   
+  <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>,
+     <a href="https://savannah.gnu.org/users/jvs";>Justin van Steijn</a>)
+  </li>
+    
+  <li><code>nn</code> - Norwegian Nynorsk 
+    (<a href="https://savannah.gnu.org/users/att";>Andreas Tolfsen</a>
+    - New coordinator needed) </li>
+
+  <li><code>pl</code> - 
+    <a href="https://savannah.gnu.org/projects/www-pl";>Polish</a> 
+    (<a href="https://savannah.gnu.org/users/jsowoc";>Jan Owoc</a>) </li>
+    
+  <li><code>pt-br</code> - 
+    <a href="https://savannah.gnu.org/projects/www-pt-br";>Brazilian
+    Portuguese</a>
+    (<a href="https://savannah.gnu.org/users/rafaelff1";>Rafael Fontenelle</a>) 
</li>
+
+  <li><code>ro</code> - 
+    <a href="https://savannah.gnu.org/projects/www-ro";>Romanian</a> 
+    (<a href="https://savannah.gnu.org/users/tct";>Tiberiu C.
+    Turbureanu</a> - New coordinator needed) </li>
+  
+  <li><code>ru</code> - 
+    <a href="https://savannah.nongnu.org/projects/www-ru";>Russian</a> 
+    (<a href="https://savannah.gnu.org/users/jimcrow";>Anatoly A. 
+    Kazantsev</a>, <a href="https://savannah.gnu.org/users/ineiev";>Pavel  
+    Kharitonov</a>) </li>
+
+  <li><code>sk</code> - 
+    <a href="https://savannah.nongnu.org/projects/www-sk";>Slovak</a> 
+    (<a href="https://savannah.gnu.org/users/dominiks";>Dominik Smatana</a> 
+    - New coordinator needed) </li>
+    
+  <li><code>sq</code> - 
+    <a href="https://savannah.gnu.org/projects/www-sq";>Albanian</a> 
+    (<a href="https://savannah.gnu.org/users/beso";>Besnik Bleta</a>)</li>
+
+  <li><code>sr</code> - 
+    <a href="https://savannah.gnu.org/projects/www-sr";>Serbian</a> 
+    (<a href="https://savannah.gnu.org/users/Ctpajgep";>Strahinya 
+    Radich</a>) </li>
+  
+  <li><code>ta</code> - 
+    <a href="https://savannah.gnu.org/projects/www-ta";>Tamil</a> 
+    (<a href="https://savannah.gnu.org/users/amachutechie";>Sri 
+    Ramadoss</a> - New coordinator needed) </li>
+
+  <li><code>th</code> - 
+    <a href="https://savannah.gnu.org/projects/www-th";>Thai</a> (New 
+    coordinator needed) </li>
+    
+  <li><code>tl</code> - 
+    <a href="https://savannah.gnu.org/projects/www-tl";>Tagalog</a> (New 
+    coordinator needed) </li>
+    
+  <li><code>tr</code> - 
+    <a href="https://savannah.gnu.org/projects/www-tr";>Turkish</a> 
+    (<a href="https://savannah.gnu.org/users/exalted";>Ali Servet 
+    D&ouml;nmez</a> - New coordinator needed) </li>
+
+  <li><code>uk</code> - 
+    <a href="https://savannah.gnu.org/projects/www-uk";>Ukrainian</a> 
+    (<a href="https://savannah.gnu.org/users/andriykopanytsia";>Andriy
+    Bandura</a>)</li>
+    
+  <li><code>zh-cn</code> - 
+    <a href="https://savannah.gnu.org/projects/www-zh-cn";>Simplified
+    Chinese</a> (<a href="https://savannah.gnu.org/users/wxie";>
+    Xie Wensheng</a>) </li>
+
+  <li><code>zh-tw</code> - 
+    <a href="https://savannah.gnu.org/projects/www-zh-tw";>Traditional
+    Chinese</a> (<a href="https://savannah.gnu.org/users/zerngjia";>
+    Cheng-Chia Tseng</a>) </li>
+  
+  <li><code>??</code> - Not available? Then this line is reserved for 
+  you.</li>
+
+  <!-- Please keep this list alphabetical. -->
+</ul>
+
+<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";>&lt;address@hidden&gt;</a>.
+</p>
+ 
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.  Broken links and other corrections or suggestions can be sent
+to <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 4.0.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright &copy; 2014, 2015, 2016, 2017 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
+Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2018/08/11 21:58:49 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
reply via email to
[Prev in Thread] Current Thread [Next in Thread]