[Top][All Lists]

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

www/server/standards README.translations.de.htm...

From: GNUN
Subject: www/server/standards README.translations.de.htm...
Date: Thu, 28 Sep 2017 12:59:58 -0400 (EDT)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     17/09/28 12:59:58

Modified files:
        server/standards: README.translations.de.html 
Added files:
        server/standards/po: README.translations.de-diff.html 

Log message:
        Automatic update by GNUnited Nations.


Index: README.translations.de.html
RCS file: /web/www/www/server/standards/README.translations.de.html,v
retrieving revision 1.80
retrieving revision 1.81
diff -u -b -r1.80 -r1.81
--- README.translations.de.html 20 Jul 2017 16:29:41 -0000      1.80
+++ README.translations.de.html 28 Sep 2017 16:59:58 -0000      1.81
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" 
value="/server/standards/README.translations.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/server/standards/po/README.translations.de.po">
+ https://www.gnu.org/server/standards/po/README.translations.de.po</a>'
+ --><!--#set var="ORIGINAL_FILE" 
+ --><!--#set var="DIFF_FILE" 
+ --><!--#set var="OUTDATED_SINCE" value="2017-07-30" --><!--#set 
var="ENGLISH_PAGE" value="/server/standards/README.translations.en.html" -->
 <!--#include virtual="/server/header.de.html" -->
 <!-- Parent-Version: 1.83 -->
@@ -9,6 +14,7 @@
 <!--#include virtual="/server/standards/po/README.translations.translist" -->
 <!--#include virtual="/server/banner.de.html" -->
+<!--#include virtual="/server/outdated.de.html" -->
 <h2 id="guide" class="section">Leitfaden zur Übersetzung von 
Internetdokumenten auf www.GNU.org</h2>
 <h3 id="intro">Einführung</h3>
@@ -699,7 +705,7 @@
 <p class="unprintable"><!-- timestamp start -->
 Letzte Änderung:
-$Date: 2017/07/20 16:29:41 $
+$Date: 2017/09/28 16:59:58 $
 <!-- timestamp end -->

Index: po/README.translations.de-diff.html
RCS file: po/README.translations.de-diff.html
diff -N po/README.translations.de-diff.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/README.translations.de-diff.html 28 Sep 2017 16:59:58 -0000      1.1
@@ -0,0 +1,689 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+&lt;!--#include virtual="/server/header.html" --&gt;
+&lt;!-- Parent-Version: 1.83 --&gt;
+&lt;title&gt;Guide to Translating Web Pages on www.gnu.org 
+- GNU Project - Free  Software Foundation&lt;/title&gt;
+&lt;!--#include virtual="/server/standards/po/README.translations.translist" 
+&lt;!--#include virtual="/server/banner.html" --&gt;
+&lt;h2 id="guide" class="section"&gt;Guide to Translating Web Pages on
+&lt;h3 id="intro"&gt;Introduction&lt;/h3&gt;
+&lt;p&gt;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.&lt;/p&gt;
+&lt;p&gt;Team Coordinators use software tools to update pages efficiently for 
+partial changes. One of these tools is a program called &lt;strong&gt;GNUnited 
+Nations&lt;/strong&gt; (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.&lt;/p&gt;
+&lt;p&gt;The Translations Manager is the person in charge of the overall 
+organization of teams and is generally involved in training new Team 
+&lt;p&gt;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.&lt;/p&gt;
+&lt;h3 id="who"&gt;Who can help&lt;/h3&gt;
+&lt;p&gt;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.&lt;/p&gt;
+  &lt;li&gt;&lt;p&gt;If you have a deep understanding of written English and a 
+    command of your native language, you can certainly engage in 
+    translation, or do proof-reading. Writing good English is not 
+  necessary.&lt;/p&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;p&gt;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.&lt;/p&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;p&gt;If you are a native English speaker, and you can read 
+    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 
+  &lt;li&gt;&lt;p&gt;If you are inclined or willing to go for the more 
+    side of the translation process, you can help further; for example, 
+    by preparing translated texts for publication.&lt;/p&gt;&lt;/li&gt;
+&lt;h3 id="how"&gt;How to Participate&lt;/h3&gt;
+  &lt;dt&gt;As a Team Member&lt;/dt&gt;
+    &lt;dd&gt;Please read the &lt;a href="#general-guide"&gt;General Guide for 
+      Translations&lt;/a&gt; below and then contact the relevant 
+      &lt;a href="#teams"&gt;translation team&lt;/a&gt;. 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 &lt;a 
+      href="mailto:address@hidden"&gt;&lt;address@hidden&gt;&lt;/a&gt;.
+    &lt;/dd&gt;
+  &lt;dt&gt;As an Occasional Contributor&lt;/dt&gt;
+    &lt;dd&gt;If you just want to submit a new translation and are not 
+      interested in collaborating regularly, follow the 
+      &lt;a href="#general-guide"&gt;General Guide for Translations&lt;/a&gt; 
+      and then send your translation to the appropriate &lt;a href="#teams"&gt;
+      Team Coordinator&lt;/a&gt; if there is one, or to the Translations 
+      Manager &lt;a 
+      href="mailto:address@hidden"&gt;&lt;address@hidden&gt;&lt;/a&gt;
+      if there is no team or coordinator for your language.&lt;/dd&gt;
+  &lt;dt&gt;As a Team Coordinator&lt;/dt&gt;
+    &lt;dd&gt;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 &lt;a 
+      href="#general-guide"&gt;General Guide for Translations&lt;/a&gt;  and 
the more 
+      specific &lt;a href="#coordinator-guide"&gt;Guide for Team 
+      &lt;/dd&gt;
+&lt;h3 id="general-guide"&gt;General Guide for Translations&lt;/h3&gt;
+&lt;p&gt;Here are our specific goals for our translated pages.&lt;/p&gt;
+&lt;h4 id="clarity"&gt;Clarity&lt;/h4&gt;
+&lt;p&gt;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.&lt;/p&gt;
+&lt;p&gt;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).&lt;/p&gt;
+&lt;h4 id="accuracy"&gt;Accuracy&lt;/h4&gt;
+&lt;p&gt;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.
+Please study the &lt;a href="/philosophy"&gt; philosophy &lt;/a&gt; of the free
+software movement, so that you can present it properly and clearly.
+The following articles will be particularly helpful:
+  &lt;li&gt;&lt;a href="/philosophy/free-sw.html"&gt;What is Free 
+  &lt;li&gt;&lt;a href="/philosophy/categories.html"&gt;Categories of Free and 
+    Nonfree Software&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href="/philosophy/words-to-avoid.html"&gt;Words to 
+  &lt;li&gt;&lt;a href="/gnu/why-gnu-linux.html"&gt;What's in a 
+  &lt;li&gt;&lt;a href="/philosophy/open-source-misses-the-point.html"&gt;Open 
+    Source Misses the Point of Free Software&lt;/a&gt;&lt;/li&gt;
+These terms and files need special attention:
+  &lt;li&gt;&lt;p&gt;&lt;strong&gt;Copyleft&lt;/strong&gt;. 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 &lt;a href="/copyleft/copyleft.html"&gt;What is 
Copyleft?&lt;/a&gt; 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 
+  &lt;li&gt;&lt;p&gt;&lt;strong&gt;Free Software&lt;/strong&gt;. 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.&lt;/p&gt;
+    &lt;p&gt;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.&lt;/p&gt;
+    &lt;p&gt;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.&lt;/p&gt;
+    &lt;p&gt;See the &lt;a 
+    href="/philosophy/fs-translations.html"&gt;Translations 
+    of the Term  &ldquo;Free Software&rdquo;&lt;/a&gt; in several 
+  &lt;/li&gt;
+  &lt;li&gt;&lt;p&gt;&lt;strong&gt;Digital Restrictions Management 
(DRM)&lt;/strong&gt;. 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.&lt;/p&gt; 
+    &lt;p&gt;However, there is a subtle ambiguity in the English term
+    &ldquo;Digital Restrictions Management&rdquo;.  It can be interpreted in 
+    ways:&lt;/p&gt;
+    &lt;ol&gt;
+      &lt;li&gt; &lt;strong&gt;Digital Management of 
+      &lt;li&gt; Management of Digital Restrictions.&lt;/li&gt;
+    &lt;/ol&gt;
+    &lt;p&gt;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;.&lt;/p&gt;
+  &lt;/li&gt;
+  &lt;li&gt;
+    &lt;p&gt;&lt;strong&gt;Should&lt;/strong&gt;. In regard to an ethical 
+    &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.&lt;/p&gt;
+    &lt;p&gt;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.&lt;/p&gt;
+  &lt;/li&gt;
+  &lt;li&gt;&lt;p&gt;&lt;strong&gt;GNU's Not Unix&lt;/strong&gt;. When 
+    &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 (&lt;span xml:lang="sv" lang="sv"&gt;
+    GNU &auml;r inte Unix&lt;/span&gt;)&rdquo;.&lt;/p&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;p&gt;Exception: The page philosophy/words-to-avoid.html is an 
+    to our usual policies about which terminology to use, because it
+    presents examples of what &lt;em&gt;not&lt;/em&gt; to say.  For instance, 
+    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.&lt;/p&gt;
+    &lt;p&gt;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.&lt;/p&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;p&gt;&lt;strong&gt;Surveillance&lt;/strong&gt;. 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.&lt;/p&gt;
+    &lt;p&gt;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.&lt;/p&gt;&lt;/li&gt;
+&lt;p&gt;For more info, see &lt;a
+Interpreters Guide&lt;/a&gt;&lt;/p&gt;
+&lt;p&gt;Before installing or before submitting your translation for 
+installation in gnu.org:&lt;/p&gt;
+  &lt;li&gt;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.&lt;/li&gt;
+  &lt;li&gt;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.&lt;/li&gt;
+&lt;h4 id="licensing"&gt;Licensing of Translations&lt;/h4&gt;
+&lt;p&gt;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.&lt;/p&gt;
+&lt;p&gt;For specific rules, see &lt;a
+Distribution Terms&lt;/a&gt; in the &lt;cite&gt;GNU Web Translators 
+&lt;h4 id="what"&gt;What to Translate&lt;/h4&gt;
+&lt;p&gt;All essays and articles in the following directories should be 
+in all available languages, but you should first browse our 
+&lt;a href="/server/standards/translations/priorities.html"&gt;Web Translation 
+  &lt;li&gt;&lt;code&gt;education/&lt;/code&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;gnu/&lt;/code&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;licenses/&lt;/code&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;philosophy/&lt;/code&gt;&lt;/li&gt;
+&lt;p&gt;Again, please coordinate with your language team before starting any 
+to get clear instructions on how to proceed and to avoid duplicating efforts.
+&lt;p&gt;&lt;em&gt;&lt;strong&gt;Note:&lt;/strong&gt;&lt;/em&gt; The material 
in the 
+&lt;code&gt;software/&lt;/code&gt; 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.&lt;/p&gt;
+&lt;h4 id="translators-manual"&gt;Translators Manual&lt;/h4&gt;
+&lt;p&gt;You may also want to read the 
+&lt;a href="/software/trans-coord/manual/web-trans/"&gt;GNU Web Translators 
+Manual&lt;/a&gt; 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 
+&lt;h3 id="coordinator-guide"&gt;Guide for Team Coordinators&lt;/h3&gt;
+&lt;p&gt;The following is an explanation of what a Team Coordinator does 
+specifically. In addition to what has already been described, a Team 
+  &lt;li&gt;&lt;p&gt;sees to it that all texts to be published are faithful to 
+    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;&lt;/p&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;p&gt;understands thoroughly how our translation system works, 
+    knows how to use the tools that we have adopted. In the following section 
+    we explain briefly how it is done.&lt;/p&gt;&lt;/li&gt;
+&lt;h4 id="tools"&gt;Tools&lt;/h4&gt;
+&lt;p&gt;We use .po (Portable Object) files to process and maintain 
+A .po file contains the original text and its translation, divided in 
+paragraphs. This is how we do it:&lt;/p&gt;
+  &lt;li&gt;&lt;p&gt;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.&lt;/p&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;p&gt;Whenever there is a change in the original HTML article, 
+    .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.&lt;/p&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;p&gt;.po files can be edited by using any .po file 
+      &lt;p&gt;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. 
+      &lt;a href="/server/standards/translations/po-how-to.html"&gt;Here is an 
+      example&lt;/a&gt;.&lt;/p&gt;&lt;/li&gt;
+&lt;p&gt;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 &lt;a
+mailing list to keep an eye on pages that are modified. You may also
+use &ldquo;&lt;em&gt;&lt;code&gt;make report 
TEAM=LANG&lt;/code&gt;&lt;/em&gt;&rdquo; if you
+have GNUN installed.&lt;/p&gt;
+&lt;h4 id="coord-manuals"&gt;Coordinators Manuals&lt;/h4&gt;
+&lt;p&gt;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:&lt;/p&gt;
+  &lt;li&gt;&lt;a href="/software/trans-coord/manual/web-trans/"&gt;GNU Web
+  Translators Manual&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href="/software/trans-coord/manual/gnun/"&gt;GNUnited 
Nations (GNUN) 
+    Manual&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href="/server/standards/README.webmastering.html"&gt;GNU Web 
+    Guidelines: For Volunteers&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href="/server/fsf-html-style-sheet.html"&gt;GNU Web Site
+  Guidelines: HTML Style Sheet&lt;/a&gt;&lt;/li&gt;
+&lt;p&gt;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 &lt;a
+of your decision. Start reading at least the first two manuals and ask
+the Translations Manager for assistance if you have any doubts.&lt;/p&gt;
+&lt;h3 id="teams"&gt;Translation Teams&lt;/h3&gt;
+&lt;span id="TranslationsUnderway"&gt;&lt;!--Some docs refer to this 
+&lt;p&gt;Volunteers to establish new teams are more than welcome and will be
+assisted during the learning process.&lt;/p&gt;
+&lt;p&gt;In the following list, the language code is followed by the name of 
+language, and by the name of the Team Coordinator.&lt;/p&gt;
+  &lt;!-- Please keep this list alphabetical--&gt;
+  &lt;li&gt;&lt;code&gt;ar&lt;/code&gt; - 
+    &lt;a 
+    (&lt;a href="https://savannah.gnu.org/users/ka2in"&gt;Fayçal 
Alami&lt;/a&gt; - 
+    New coordinator needed) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;az&lt;/code&gt; - Azerbaijani 
+    (&lt;a href="https://savannah.gnu.org/users/igrar"&gt;Igrar 
Huseynov&lt;/a&gt; - 
+    New coordinator needed) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;bg&lt;/code&gt; - 
+    &lt;a 
+    (&lt;a href="https://savannah.gnu.org/users/yavor"&gt;Yavor 
Doganov&lt;/a&gt; -
+    New coordinator needed)&lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;bn&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-bn"&gt;Bengali&lt;/a&gt; 
+    (&lt;a href="https://savannah.gnu.org/users/suzan"&gt;Khandakar Mujahidul
+    Islam&lt;/a&gt; - New coordinator needed) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;ca&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-ca"&gt;Catalan&lt;/a&gt; 
+    (&lt;a href="https://savannah.gnu.org/users/puigpe"&gt;Miquel 
+    Puigpelat&lt;/a&gt;) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;cs&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-cs"&gt;Czech&lt;/a&gt;
+    (&lt;a href="https://savannah.gnu.org/users/franta"&gt;František 
+  &lt;li&gt;&lt;code&gt;da&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-da"&gt;Danish&lt;/a&gt; 
+    (&lt;a href="https://savannah.gnu.org/users/erikg"&gt;Erik 
Gravgaard&lt;/a&gt; - 
+    New coordinator needed) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;de&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-de"&gt;German&lt;/a&gt; 
+    (&lt;a href="https://savannah.gnu.org/users/joeko"&gt;Joerg 
+  &lt;li&gt;&lt;code&gt;el&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-el"&gt;Greek&lt;/a&gt; 
+    (&lt;a href="https://savannah.gnu.org/users/gzarkadas"&gt;Georgios 
+    Zarkadas&lt;/a&gt;) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;eo&lt;/code&gt; - 
+    &lt;a 
+    (&lt;a href="https://savannah.gnu.org/users/civodul"&gt;Ludovic 
+    Court&egrave;s&lt;/a&gt; - New coordinator needed) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;es&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-es"&gt;Spanish&lt;/a&gt; 
+    (&lt;a href="https://savannah.gnu.org/users/dora"&gt;Dora 
+    &lt;a href="https://savannah.gnu.org/users/jfrtnaga"&gt;Javier Fernández
+    Retenaga&lt;/a&gt;)&lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;fa&lt;/code&gt; - 
+    &lt;a 
+    (&lt;a href="https://savannah.gnu.org/users/esmaeeli"&gt;Abbas Esmaeeli
+    Some&lsquo;eh&lt;/a&gt;) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;fi&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-fi"&gt;Finnish&lt;/a&gt; 
+    (&lt;a href="https://savannah.gnu.org/users/solarius"&gt;Ville&lt;/a&gt; - 
+    coordinator needed)&lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;fr&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-fr"&gt;French&lt;/a&gt; 
+    (&lt;a href="https://savannah.gnu.org/users/barbier"&gt;Denis 
+     &lt;a href="https://savannah.gnu.org/users/th_g"&gt;Thérèse 
+  &lt;li&gt;&lt;code&gt;he&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-he"&gt;Hebrew&lt;/a&gt; 
+    coordinator needed) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;hr&lt;/code&gt; - 
+    &lt;a 
+    (&lt;a href="https://savannah.gnu.org/users/mist"&gt;Martina 
Bebek&lt;/a&gt; -
+    New coordinator needed)&lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;id&lt;/code&gt; - 
+    &lt;a 
+    (New coordinator needed) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;it&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-it"&gt;Italian&lt;/a&gt; 
+    (&lt;a href="https://savannah.gnu.org/users/pescetti"&gt;Andrea 
+    Pescetti&lt;/a&gt;) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;ja&lt;/code&gt; - 
+    &lt;a 
+    (&lt;a href="https://savannah.gnu.org/users/gniibe"&gt;NIIBE 
+  &lt;li&gt;&lt;code&gt;ko&lt;/code&gt; -
+    &lt;a href="https://savannah.gnu.org/projects/www-ko"&gt;Korean&lt;/a&gt; 
+    (&lt;a href="https://savannah.gnu.org/users/blueguy"&gt;Jongmin 
Yoon&lt;/a&gt;) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;ku&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-ku"&gt;Kurdish&lt;/a&gt; 
+    coordinator needed) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;ml&lt;/code&gt; - 
+    &lt;a 
+    (New coordinator needed) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;nb&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-nb"&gt;Norwegian 
+    Bokm&aring;l&lt;/a&gt; (&lt;a href="https://savannah.gnu.org/users/att"&gt;
+    Andreas Tolfsen&lt;/a&gt;
+    - New coordinator needed) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;nl&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-nl"&gt;Dutch&lt;/a&gt; 
+    (&lt;a href="https://savannah.gnu.org/users/tuijldert"&gt;Tom 
+     &lt;a href="https://savannah.gnu.org/users/jvs"&gt;Justin van 
+  &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;nn&lt;/code&gt; - Norwegian Nynorsk 
+    (&lt;a href="https://savannah.gnu.org/users/att"&gt;Andreas 
+    - New coordinator needed) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;pl&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-pl"&gt;Polish&lt;/a&gt; 
+    (&lt;a href="https://savannah.gnu.org/users/jsowoc"&gt;Jan Owoc&lt;/a&gt;) 
+  &lt;li&gt;&lt;code&gt;pt-br&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-pt-br"&gt;Brazilian
+    Portuguese&lt;/a&gt;
+    (New coordinator needed) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;ro&lt;/code&gt; - 
+    &lt;a 
+    (&lt;a href="https://savannah.gnu.org/users/tct"&gt;Tiberiu C.
+    Turbureanu&lt;/a&gt; - New coordinator needed) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;ru&lt;/code&gt; - 
+    &lt;a 
+    (&lt;a href="https://savannah.gnu.org/users/jimcrow"&gt;Anatoly A. 
+    Kazantsev&lt;/a&gt;, &lt;a 
+    Kharitonov&lt;/a&gt;) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;sk&lt;/code&gt; - 
+    &lt;a 
+    (&lt;a href="https://savannah.gnu.org/users/dominiks"&gt;Dominik 
+    - New coordinator needed) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;sq&lt;/code&gt; - 
+    &lt;a 
+    (&lt;a href="https://savannah.gnu.org/users/beso"&gt;Besnik 
+  &lt;li&gt;&lt;code&gt;sr&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-sr"&gt;Serbian&lt;/a&gt; 
+    (&lt;a href="https://savannah.gnu.org/users/Ctpajgep"&gt;Strahinya 
+    Radich&lt;/a&gt; - New coordinator needed) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;ta&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-ta"&gt;Tamil&lt;/a&gt; 
+    (&lt;a href="https://savannah.gnu.org/users/amachutechie"&gt;Sri 
+    Ramadoss&lt;/a&gt; - New coordinator needed) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;th&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-th"&gt;Thai&lt;/a&gt; 
+    coordinator needed) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;tl&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-tl"&gt;Tagalog&lt;/a&gt; 
+    coordinator needed) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;tr&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-tr"&gt;Turkish&lt;/a&gt; 
+    (&lt;a href="https://savannah.gnu.org/users/exalted"&gt;Ali Servet 
+    D&ouml;nmez&lt;/a&gt; - New coordinator needed) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;uk&lt;/code&gt; - 
+    &lt;a 
+    (&lt;a href="https://savannah.gnu.org/users/andriykopanytsia"&gt;Andriy
+    Bandura&lt;/a&gt;)&lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;zh-cn&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-zh-cn"&gt;Simplified
+    Chinese&lt;/a&gt; (&lt;a <span 
+    Nan Deng&lt;/a&gt;, &lt;a 
+    Xu&lt;/a&gt;, &lt;a 
+    Xiaobin&lt;/a&gt; - New coordinator needed)</strong></del></span> <span 
+    Xie Wensheng&lt;/a&gt;)</em></ins></span> &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;zh-tw&lt;/code&gt; - 
+    &lt;a href="https://savannah.gnu.org/projects/www-zh-cn"&gt;Traditional
+    Chinese&lt;/a&gt; (&lt;a href="https://savannah.gnu.org/users/zerngjia"&gt;
+    Cheng-Chia Tseng&lt;/a&gt;) &lt;/li&gt;
+  &lt;li&gt;&lt;code&gt;??&lt;/code&gt; - Not available? Then this line is 
reserved for 
+  you.&lt;/li&gt;
+  &lt;!-- Please keep this list alphabetical. --&gt;
+&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; &lt;em&gt;English&lt;/em&gt; 
(&lt;code&gt;en&lt;/code&gt;) is a special
+case. The bulk of the site is written in English, which is the de-facto
+language of the GNU Project. We &lt;em&gt;occasionally&lt;/em&gt; 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 &lt;a 
+&lt;/div&gt;&lt;!-- for id="content", starts in the include above --&gt;
+&lt;!--#include virtual="/server/footer.html" --&gt;
+&lt;div id="footer"&gt;
+&lt;div class="unprintable"&gt;
+&lt;p&gt;Please send general FSF &amp; GNU inquiries to
+&lt;a href="mailto:address@hidden"&gt;&lt;address@hidden&gt;&lt;/a&gt;.
+There are also &lt;a href="/contact/"&gt;other ways to contact&lt;/a&gt;
+the FSF.  Broken links and other corrections or suggestions can be sent
+to &lt;a 
+&lt;p&gt;&lt;!-- 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 &lt;a href="mailto:address@hidden"&gt;
+        &lt;address@hidden&gt;&lt;/a&gt;.&lt;/p&gt;
+        &lt;p&gt;For information on coordinating and submitting translations of
+        our web pages, see &lt;a
+        href="/server/standards/README.translations.html"&gt;Translations
+        README&lt;/a&gt;. --&gt;
+Please see the &lt;a
+README&lt;/a&gt; for information on coordinating and submitting translations
+of this article.&lt;/p&gt;
+&lt;!-- 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. --&gt;
+&lt;p&gt;Copyright &copy; 2014, 2015, 2016, 2017 Free Software Foundation, 
+&lt;p&gt;This page is licensed under a &lt;a rel="license"
+Commons Attribution-NoDerivatives 4.0 International 
+&lt;!--#include virtual="/server/bottom-notes.html" --&gt;
+&lt;p class="unprintable"&gt;Updated:
+&lt;!-- timestamp start --&gt;
+$Date: 2017/09/28 16:59:58 $
+&lt;!-- timestamp end --&gt;

reply via email to

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