Ergebnis für URL: http://www.gnu.org/server/standards/README.translations.html #[1]alternate [2]English [3]català [4]Deutsch [5]français [6]æU97¥æU9C¬èªU9E
[7]português [8]Shqip [9]ç®U80ä½U93ä¸æU96U87
[10]Skip to main text
[11]Free Software Supporter: email address_____ Sign up
[12]JOIN THE FSF
[13] [A GNU head] GNU Operating System
Supported by the [14]Free Software Foundation
[15] [Search www.gnu.org]
[16] [Other languages]
[17]Site navigation [18]Skip
* [19]ABOUT GNU
* [20]PHILOSOPHY
* [21]LICENSES
* [22]EDUCATION
* [23]SOFTWARE
* [24]DISTROS
* [25]DOCS
* [26]MALWARE
* [27]HELP GNU
* [28]AUDIO & VIDEO
* [29]GNU ART
* [30]FUN
* [31]GNU'S WHO?
* [32]SOFTWARE DIRECTORY
* [33]HARDWARE
* [34]SITEMAP
Guide to Translating Web Pages on www.gnu.org
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.
Team Coordinators use software tools to update pages efficiently for partial
changes. One of these tools is a program called GNUnited Nations (GNUN) that
makes it very easy to maintain and keep track of translations that need to be
updated; it was developed ad hoc by our current GNU Translations Manager Yavor
Doganov.
The Translations Manager is the person in charge of the overall organization of
teams and is generally involved in training new Team Coordinators.
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.
Who can Help
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.
* 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.
* 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.
* 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--you can indicate possible errors
and explain the intended meaning, and others can retranslate that part.
* 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.
How to Participate
As a Team Member
Please read the [35]General Guide for Translations below and then contact
the relevant [36]translation team. 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
[37].
As an Occasional Contributor
If you just want to submit a new translation and are not interested in
collaborating regularly, follow the [38]General Guide for Translations
below and then send your translation to the appropriate [39]Team
Coordinator if there is one, or to the Translations Manager
[40] if there is no team or coordinator for your
language.
As a Team Coordinator
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 [41]General Guide for
Translations and the more specific [42]Guide for Team Coordinators.
General Guide for Translations
Here are our specific goals for our translated pages.
Clarity
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.
In pages meant for the general public, please avoid words that are not found in
common dictionaries, except for our special terms such as "GNU" and "copyleft"
(see the list below).
Accuracy
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 [43]philosophy of the free software movement, so that you can
present it properly and clearly. The following articles will be particularly
helpful:
* [44]What is Free Software?
* [45]Categories of Free and Nonfree Software
* [46]Words to Avoid
* [47]What's in a Name?
* [48]Open Source Misses the Point of Free Software
These terms and files need special attention:
* Copyleft. 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 article [49]What is
Copyleft? 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.
* Free Software. Most languages have a word for free-as-in-freedom and another
word for gratis (zero price). In gnu.org we generally use "free" only to
refer to freedom, and we say "gratis" when we mean zero price. Thus, please
translate "free" using the word that means free-as-in-freedom, not the one
that refers to price.
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 "free". 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.
However, even in these old pages, the word you normally use to translate
"free" in "free software" should be the one that refers to freedom.
See the [50]Translations of the Term "Free Software" in several languages.
* Digital Restrictions Management (DRM). 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.
However, there is a subtle ambiguity in the English term "Digital
Restrictions Management". It can be interpreted in two ways:
1. Digital Management of Restrictions.
2. Management of Digital Restrictions.
In many languages these require different wording. The correct meaning is the
first one, so translations should make this clear. Likewise with "rights"
instead of "restrictions".
* Should. In regard to an ethical issue, "should" means it would be wrong to do
anything else. For instance, the page entitled "Why Software Should Be Free"
explains why it is wrong to make software nonfree in the actual world we live
in.
Therefore, please translate "should" using a verb form that implies a strong
ethical obligation. Don't translate it in a way that means "it would be
preferable for software to be free" or "in an ideal world, software would be
free". Those are not strong enough.
* GNU's Not Unix. 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 ( GNU är inte Unix)".
* 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 not to say. For instance, in general we shun the term "Digital Rights
Management". However, we cite that term in philosophy/words-to-avoid.html in
order to advise others to shun it.
As a translator, it is best if you follow the English text. Where the English
text says "Digital Rights Management", translate that. Where the English text
says "Digital Restrictions Management", translate that.
* Surveillance. 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 "surveillance" is used more widely; it may
describe the benevolent watch of a shepherd over his sheep or of a teacher
over her students.
When translating "surveillance", please make sure you don't use a word which
could be interpreted as "benevolent watch". If there is no specialized term,
the word which means "spying" may be adequate in the context of proprietary
software.
For more info, see [51]Interpreters Guide
Before installing or before submitting your translation for installation in
gnu.org:
* 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.
* 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.
Licensing of Translations
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.
For specific rules, see [52]Distribution Terms in the GNU Web Translators Manual.
What to Translate
We accept contributions of translations of all articles in all languages, but you
should first browse our [53]Web Translation Priorities.
Again, please coordinate with your language team before starting any work, to get
clear instructions on how to proceed and to avoid duplicating efforts.
Translators Manual
You may also want to read the [54]GNU Web Translators Manual 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.
Guide for Team Coordinators
The following is an explanation of what a Team Coordinator does specifically. In
addition to what has already been described, a Team Coordinator:
* 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;
* 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.
Tools
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:
* 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.
* 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.
* .po files can be edited by using any .po file editor.
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.
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 [55]www-commits mailing list to keep an eye on pages that are modified.
You may also use "make report TEAM=LANG" if you have GNUN installed.
Coordinators Manuals
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:
* [56]GNU Web Translators Manual
* [57]GNUnited Nations (GNUN) Manual
* [58]GNU Web Site Guidelines: For Volunteers
* [59]GNU Web Site Guidelines: HTML Style Sheet
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
[60] of your decision. Start reading at least the first
two manuals and ask the Translations Manager for assistance if you have any
doubts.
Translation Teams
Volunteers to establish new teams are more than welcome and will be assisted
during the learning process.
In the following list, the language code is followed by the name of the language,
and by the name of the Team Coordinator.
* ar - [61]Arabic ([62]Fayçal Alami - New coordinator needed)
* az - Azerbaijani (New coordinator needed)
* bg - [63]Bulgarian ([64]Yavor Doganov - New coordinator needed)
* bn - [65]Bengali (New coordinator needed)
* ca - [66]Catalan ([67]Miquel Puigpelat - New coordinator needed)
* cs - [68]Czech ([69]Frantisek Kucera)
* da - [70]Danish (New coordinator needed)
* de - [71]German ([72]Joerg Kohne - New coordinator needed)
* el - [73]Greek ([74]Georgios Zarkadas - New coordinator needed)
* eo - [75]Esperanto ([76]Ludovic Courtès - New coordinator needed)
* es - [77]Spanish ([78]Dora Scilipoti, [79]Javier Fernández Retenaga)
* fa - [80]Farsi/Persian ([81]Amin Bandali)
* fi - [82]Finnish (New coordinator needed)
* fr - [83]French ([84]Denis Barbier, [85]Thérèse Godefroy)
* he - [86]Hebrew (New coordinator needed)
* hr - [87]Croatian ([88]Martina Bebek - New coordinator needed)
* id - [89]Indonesian (New coordinator needed)
* it - [90]Italian ([91]Andrea Pescetti)
* ja - [92]Japanese ([93]NIIBE Yutaka)
* ko - [94]Korean ([95]Jongmin Yoon - New coordinator needed)
* ku - [96]Kurdish (New coordinator needed)
* ml - [97]Malayalam ([98]Aiswarya Kaitheri Kandoth)
* nb - [99]Norwegian Bokmål (New coordinator needed)
* nl - [100]Dutch ([101]Tom Uijldert, [102]Justin van Steijn - New coordinator
needed)
* nn - Norwegian Nynorsk (New coordinator needed)
* pl - [103]Polish ([104]Jan Owoc)
* pt-br - [105]Brazilian Portuguese ([106]Rafael Fontenelle - New coordinator
needed)
* ro - [107]Romanian ([108]Tiberiu C. Turbureanu - New coordinator needed)
* ru - [109]Russian ([110]Anatoly A. Kazantsev, [111]Pavel Kharitonov)
* sk - [112]Slovak ([113]Dominik Smatana - New coordinator needed)
* sq - [114]Albanian ([115]Besnik Bleta)
* sr - [116]Serbian ([117]Strahinya Radich - New coordinator needed)
* ta - [118]Tamil ([119]Sri Ramadoss - New coordinator needed)
* th - [120]Thai (New coordinator needed)
* tl - [121]Tagalog (New coordinator needed)
* tr - [122]Turkish ([123]T. E. Kalayci)
* uk - [124]Ukrainian ([125]Andriy Bandura - New coordinator needed)
* zh-cn - [126]Simplified Chinese ([127]Xie Wensheng)
* zh-tw - [128]Traditional Chinese ([129]Po-Yen Huang)
* ?? - Not available? Then this line is reserved for you.
Note: English (en) is a special case. The bulk of the site is written in English,
which is the de-facto language of the GNU Project. We occasionally 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
[130].
____________________________________________________________________________
[131]^
[132]BACK TO TOP
[133]Set language
Available for this page:
[en] [134]English [ca] [135]català [de] [136]Deutsch [fr] [137]français
[ja] [138]¥¬ [pt-br] [139]português [sq] [140]Shqip [zh-cn] [141]
____________________________________________________________________________
[142]BACK TO TOP ^
[143] [FSF logo] "The Free Software Foundation (FSF) is a nonprofit with a
worldwide mission to promote computer user freedom. We defend the rights of
all software users".
[144]JOIN [145]DONATE [146]SHOP
Please send general FSF & GNU inquiries to [147]. There are also
[148]other ways to contact the FSF. Broken links and other corrections or
suggestions can be sent to [149].
Please see the [150]Translations README for information on coordinating and
contributing translations of this article.
Copyright © 2014, 2015, 2016, 2017, 2019, 2020, 2021, 2023 Free Software
Foundation, Inc.
This page is licensed under a [151]Creative Commons Attribution-NoDerivatives 4.0
International License.
[152]Copyright Infringement Notification
Updated: $Date: 2023/04/01 13:10:56 $
References
1. http://www.gnu.org/server/standards/README.translations.html
2. http://www.gnu.org/server/standards/README.translations.en.html
3. http://www.gnu.org/server/standards/README.translations.ca.html
4. http://www.gnu.org/server/standards/README.translations.de.html
5. http://www.gnu.org/server/standards/README.translations.fr.html
6. http://www.gnu.org/server/standards/README.translations.ja.html
7. http://www.gnu.org/server/standards/README.translations.pt-br.html
8. http://www.gnu.org/server/standards/README.translations.sq.html
9. http://www.gnu.org/server/standards/README.translations.zh-cn.html
10. http://www.gnu.org/server/standards/README.translations.html#content
11. http://www.fsf.org/fss
12. https://www.fsf.org/associate/support_freedom?referrer=4052
13. http://www.gnu.org/
14. http://www.gnu.org/server/standards/README.translations.html#mission-statement
15. http://www.gnu.org/cgi-bin/estseek.cgi
16. http://www.gnu.org/server/standards/README.translations.html#language-container
17. http://www.gnu.org/server/standards/README.translations.html#navigation
18. http://www.gnu.org/server/standards/README.translations.html#content
19. http://www.gnu.org/gnu/gnu.html
20. http://www.gnu.org/philosophy/philosophy.html
21. http://www.gnu.org/licenses/licenses.html
22. http://www.gnu.org/education/education.html
23. http://www.gnu.org/software/software.html
24. http://www.gnu.org/distros/distros.html
25. http://www.gnu.org/doc/doc.html
26. http://www.gnu.org/proprietary/proprietary.html
27. http://www.gnu.org/help/help.html
28. http://www.gnu.org/audio-video/audio-video.html
29. http://www.gnu.org/graphics/graphics.html
30. http://www.gnu.org/fun/humor.html
31. http://www.gnu.org/people/people.html
32. http://directory.fsf.org/
33. https://h-node.org/
34. http://www.gnu.org/server/sitemap.html
35. http://www.gnu.org/server/standards/README.translations.html#general-guide
36. http://www.gnu.org/server/standards/README.translations.html#teams
37. mailto:web-translators@gnu.org
38. http://www.gnu.org/server/standards/README.translations.html#general-guide
39. http://www.gnu.org/server/standards/README.translations.html#teams
40. mailto:web-translators@gnu.org
41. http://www.gnu.org/server/standards/README.translations.html#general-guide
42. http://www.gnu.org/server/standards/README.translations.html#coordinator-guide
43. http://www.gnu.org/philosophy
44. http://www.gnu.org/philosophy/free-sw.html
45. http://www.gnu.org/philosophy/categories.html
46. http://www.gnu.org/philosophy/words-to-avoid.html
47. http://www.gnu.org/gnu/why-gnu-linux.html
48. http://www.gnu.org/philosophy/open-source-misses-the-point.html
49. http://www.gnu.org/copyleft/copyleft.html
50. http://www.gnu.org/philosophy/fs-translations.html
51. http://www.gnu.org/server/standards/translations/interpreters-guide.html
52. http://www.gnu.org/software/trans-coord/manual/web-trans/html_node/Distribution-Terms.html
53. http://www.gnu.org/server/standards/translations/priorities.html
54. http://www.gnu.org/software/trans-coord/manual/web-trans/
55. http://lists.gnu.org/mailman/listinfo/www-commits
56. http://www.gnu.org/software/trans-coord/manual/web-trans/
57. http://www.gnu.org/software/trans-coord/manual/gnun/
58. http://www.gnu.org/server/standards/README.webmastering.html
59. http://www.gnu.org/server/fsf-html-style-sheet.html
60. mailto:web-translators@gnu.org
61. http://savannah.gnu.org/projects/www-ar
62. http://savannah.gnu.org/users/ka2in
63. http://savannah.gnu.org/projects/www-bg
64. http://savannah.gnu.org/users/yavor
65. http://savannah.gnu.org/projects/www-bn
66. http://savannah.gnu.org/projects/www-ca
67. http://savannah.gnu.org/users/puigpe
68. http://savannah.gnu.org/projects/www-cs
69. http://savannah.gnu.org/users/franta
70. http://savannah.gnu.org/projects/www-da
71. http://savannah.gnu.org/projects/www-de
72. http://savannah.gnu.org/users/joeko
73. http://savannah.gnu.org/projects/www-el
74. http://savannah.gnu.org/users/gzarkadas
75. http://savannah.gnu.org/projects/www-eo
76. http://savannah.gnu.org/users/civodul
77. http://savannah.gnu.org/projects/www-es
78. http://savannah.gnu.org/users/dora
79. http://savannah.gnu.org/users/jfrtnaga
80. http://savannah.gnu.org/projects/www-fa
81. http://savannah.gnu.org/users/bandali
82. http://savannah.gnu.org/projects/www-fi
83. http://savannah.gnu.org/projects/www-fr
84. http://savannah.gnu.org/users/barbier
85. http://savannah.gnu.org/users/th_g
86. http://savannah.gnu.org/projects/www-he
87. http://savannah.gnu.org/projects/www-hr
88. http://savannah.gnu.org/users/mist
89. http://savannah.gnu.org/projects/www-id
90. http://savannah.gnu.org/projects/www-it
91. http://savannah.gnu.org/users/pescetti
92. http://savannah.gnu.org/projects/www-ja
93. http://savannah.gnu.org/users/gniibe
94. http://savannah.gnu.org/projects/www-ko
95. http://savannah.gnu.org/users/blueguy
96. http://savannah.gnu.org/projects/www-ku
97. http://savannah.gnu.org/projects/www-ml
98. http://savannah.gnu.org/users/aiswarya
99. http://savannah.gnu.org/projects/www-nb
100. http://savannah.gnu.org/projects/www-nl
101. http://savannah.gnu.org/users/tuijldert
102. http://savannah.gnu.org/users/jvs
103. http://savannah.gnu.org/projects/www-pl
104. http://savannah.gnu.org/users/jsowoc
105. http://savannah.gnu.org/projects/www-pt-br
106. http://savannah.gnu.org/users/rafaelff1
107. http://savannah.gnu.org/projects/www-ro
108. http://savannah.gnu.org/users/tct
109. http://savannah.gnu.org/projects/www-ru
110. http://savannah.gnu.org/users/jimcrow
111. http://savannah.gnu.org/users/ineiev
112. http://savannah.gnu.org/projects/www-sk
113. http://savannah.gnu.org/users/dominiks
114. http://savannah.gnu.org/projects/www-sq
115. http://savannah.gnu.org/users/beso
116. http://savannah.gnu.org/projects/www-sr
117. http://savannah.gnu.org/users/Ctpajgep
118. http://savannah.gnu.org/projects/www-ta
119. http://savannah.gnu.org/users/amachutechie
120. http://savannah.gnu.org/projects/www-th
121. http://savannah.gnu.org/projects/www-tl
122. http://savannah.gnu.org/projects/www-tr
123. http://savannah.gnu.org/users/tekrei
124. http://savannah.gnu.org/projects/www-uk
125. http://savannah.gnu.org/users/andriykopanytsia
126. http://savannah.gnu.org/projects/www-zh-cn
127. http://savannah.gnu.org/users/wxie
128. http://savannah.gnu.org/projects/www-zh-tw
129. http://savannah.gnu.org/users/s8321414
130. mailto:web-translators@gnu.org
131. http://www.gnu.org/server/standards/README.translations.html#top
132. http://www.gnu.org/server/standards/README.translations.html#top
133. http://www.gnu.org/server/select-language.html?callback=/server/standards/README.translations.html
134. http://www.gnu.org/server/standards/README.translations.en.html
135. http://www.gnu.org/server/standards/README.translations.ca.html
136. http://www.gnu.org/server/standards/README.translations.de.html
137. http://www.gnu.org/server/standards/README.translations.fr.html
138. http://www.gnu.org/server/standards/README.translations.ja.html
139. http://www.gnu.org/server/standards/README.translations.pt-br.html
140. http://www.gnu.org/server/standards/README.translations.sq.html
141. http://www.gnu.org/server/standards/README.translations.zh-cn.html
142. http://www.gnu.org/server/standards/README.translations.html#header
143. http://www.fsf.org/
144. http://www.fsf.org/associate/support_freedom?referrer=4052
145. http://donate.fsf.org/
146. http://shop.fsf.org/
147. mailto:gnu@gnu.org
148. http://www.gnu.org/contact/
149. mailto:web-translators@gnu.org
150. http://www.gnu.org/server/standards/README.translations.html
151. http://creativecommons.org/licenses/by-nd/4.0/
152. http://www.fsf.org/about/dmca-notice
Usage: http://www.kk-software.de/kklynxview/get/URL
e.g. http://www.kk-software.de/kklynxview/get/http://www.kk-software.de
Errormessages are in German, sorry ;-)