1 # SOME DESCRIPTIVE TITLE
2 # Copyright (C) YEAR Free Software Foundation, Inc.
3 # This file is distributed under the same license as the PACKAGE package.
4 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
9 "Project-Id-Version: PACKAGE VERSION\n"
10 "POT-Creation-Date: 2011-03-03 11:18-0400\n"
11 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
12 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
13 "Language-Team: LANGUAGE <LL@li.org>\n"
16 "Content-Type: text/plain; charset=UTF-8\n"
17 "Content-Transfer-Encoding: 8bit\n"
19 #. type: Content of: <chapter><title>
21 msgid "Internationalization and Translations"
24 #. type: Content of: <chapter><para>
27 "Debian supports an ever-increasing number of natural languages. Even if you "
28 "are a native English speaker and do not speak any other language, it is part "
29 "of your duty as a maintainer to be aware of issues of internationalization "
30 "(abbreviated i18n because there are 18 letters between the 'i' and the 'n' "
31 "in internationalization). Therefore, even if you are ok with English-only "
32 "programs, you should read most of this chapter."
35 #. type: Content of: <chapter><para>
38 "According to <ulink url=\"&url-i18n-intro;\">Introduction to i18n</ulink> "
39 "from Tomohiro KUBOTA, I18N (internationalization) means modification of a "
40 "software or related technologies so that a software can potentially handle "
41 "multiple languages, customs, and so on in the world, while L10N "
42 "(localization) means implementation of a specific language for an already "
43 "internationalized software."
46 #. type: Content of: <chapter><para>
49 "l10n and i18n are interconnected, but the difficulties related to each of "
50 "them are very different. It's not really difficult to allow a program to "
51 "change the language in which texts are displayed based on user settings, but "
52 "it is very time consuming to actually translate these messages. On the "
53 "other hand, setting the character encoding is trivial, but adapting the code "
54 "to use several character encodings is a really hard problem."
57 #. type: Content of: <chapter><para>
60 "Setting aside the i18n problems, where no general guideline can be given, "
61 "there is actually no central infrastructure for l10n within Debian which "
62 "could be compared to the buildd mechanism for porting. So most of the work "
63 "has to be done manually."
66 #. type: Content of: <chapter><section><title>
68 msgid "How translations are handled within Debian"
71 #. type: Content of: <chapter><section><para>
74 "Handling translation of the texts contained in a package is still a manual "
75 "task, and the process depends on the kind of text you want to see "
79 #. type: Content of: <chapter><section><para>
82 "For program messages, the gettext infrastructure is used most of the time. "
83 "Most of the time, the translation is handled upstream within projects like "
84 "the <ulink url=\"&url-l10n-tp;\">Free Translation Project</ulink>, the "
85 "<ulink url=\"&url-l10n-gnome;\">Gnome translation Project</ulink> or the "
86 "<ulink url=\"&url-l10n-kde;\">KDE one</ulink>. The only centralized "
87 "resource within Debian is the <ulink url=\"&url-l10n;\">Central Debian "
88 "translation statistics</ulink>, where you can find some statistics about the "
89 "translation files found in the actual packages, but no real infrastructure "
90 "to ease the translation process."
93 #. type: Content of: <chapter><section><para>
96 "An effort to translate the package descriptions started long ago, even if "
97 "very little support is offered by the tools to actually use them (i.e., only "
98 "APT can use them, when configured correctly). Maintainers don't need to do "
99 "anything special to support translated package descriptions; translators "
100 "should use the <ulink url=\"&url-ddtp;\">Debian Description Translation "
101 "Project (DDTP)</ulink>."
104 #. type: Content of: <chapter><section><para>
107 "For <systemitem role=\"package\">debconf</systemitem> templates, maintainers "
108 "should use the <systemitem role=\"package\">po-debconf</systemitem> package "
109 "to ease the work of translators, who could use the DDTP to do their work "
110 "(but the French and Brazilian teams don't). Some statistics can be found "
111 "both on the <ulink url=\"&url-ddtp;\">DDTP site</ulink> (about what is "
112 "actually translated), and on the <ulink url=\"&url-l10n;\">Central Debian "
113 "translation statistics</ulink> site (about what is integrated in the "
117 #. type: Content of: <chapter><section><para>
120 "For web pages, each l10n team has access to the relevant VCS, and the "
121 "statistics are available from the Central Debian translation statistics "
125 #. type: Content of: <chapter><section><para>
128 "For general documentation about Debian, the process is more or less the same "
129 "as for the web pages (the translators have access to the VCS), but there are "
130 "no statistics pages."
133 #. type: Content of: <chapter><section><para>
136 "For package-specific documentation (man pages, info documents, other "
137 "formats), almost everything remains to be done."
140 #. type: Content of: <chapter><section><para>
143 "Most notably, the KDE project handles translation of its documentation in "
144 "the same way as its program messages."
147 #. type: Content of: <chapter><section><para>
150 "There is an effort to handle Debian-specific man pages within a <ulink "
151 "url=\"&url-cvsweb;manpages/?cvsroot=debian-doc\">specific VCS "
152 "repository</ulink>."
155 #. type: Content of: <chapter><section><title>
157 msgid "I18N & L10N FAQ for maintainers"
160 #. type: Content of: <chapter><section><para>
163 "This is a list of problems that maintainers may face concerning i18n and "
164 "l10n. While reading this, keep in mind that there is no real consensus on "
165 "these points within Debian, and that this is only advice. If you have a "
166 "better idea for a given problem, or if you disagree on some points, feel "
167 "free to provide your feedback, so that this document can be enhanced."
170 #. type: Content of: <chapter><section><section><title>
172 msgid "How to get a given text translated"
175 #. type: Content of: <chapter><section><section><para>
178 "To translate package descriptions or <systemitem "
179 "role=\"package\">debconf</systemitem> templates, you have nothing to do; the "
180 "DDTP infrastructure will dispatch the material to translate to volunteers "
181 "with no need for interaction from your part."
184 #. type: Content of: <chapter><section><section><para>
187 "For all other material (gettext files, man pages, or other documentation), "
188 "the best solution is to put your text somewhere on the Internet, and ask on "
189 "debian-i18n for a translation in different languages. Some translation team "
190 "members are subscribed to this list, and they will take care of the "
191 "translation and of the reviewing process. Once they are done, you will get "
192 "your translated document from them in your mailbox."
195 #. type: Content of: <chapter><section><section><title>
197 msgid "How to get a given translation reviewed"
200 #. type: Content of: <chapter><section><section><para>
203 "From time to time, individuals translate some texts in your package and will "
204 "ask you for inclusion of the translation in the package. This can become "
205 "problematic if you are not fluent in the given language. It is a good idea "
206 "to send the document to the corresponding l10n mailing list, asking for a "
207 "review. Once it has been done, you should feel more confident in the "
208 "quality of the translation, and feel safe to include it in your package."
211 #. type: Content of: <chapter><section><section><title>
213 msgid "How to get a given translation updated"
216 #. type: Content of: <chapter><section><section><para>
219 "If you have some translations of a given text lying around, each time you "
220 "update the original, you should ask the previous translator to update the "
221 "translation with your new changes. Keep in mind that this task takes time; "
222 "at least one week to get the update reviewed and all."
225 #. type: Content of: <chapter><section><section><para>
228 "If the translator is unresponsive, you may ask for help on the corresponding "
229 "l10n mailing list. If everything fails, don't forget to put a warning in "
230 "the translated document, stating that the translation is somehow outdated, "
231 "and that the reader should refer to the original document if possible."
234 #. type: Content of: <chapter><section><section><para>
237 "Avoid removing a translation completely because it is outdated. Old "
238 "documentation is often better than no documentation at all for non-English "
242 #. type: Content of: <chapter><section><section><title>
244 msgid "How to handle a bug report concerning a translation"
247 #. TODO: add the i18n tag to the bug?
248 #. type: Content of: <chapter><section><section><para>
251 "The best solution may be to mark the bug as forwarded to upstream, and "
252 "forward it to both the previous translator and his/her team (using the "
253 "corresponding debian-l10n-XXX mailing list)."
256 #. type: Content of: <chapter><section><title>
258 msgid "I18N & L10N FAQ for translators"
261 #. type: Content of: <chapter><section><para>
264 "While reading this, please keep in mind that there is no general procedure "
265 "within Debian concerning these points, and that in any case, you should "
266 "collaborate with your team and the package maintainer."
269 #. type: Content of: <chapter><section><section><title>
271 msgid "How to help the translation effort"
274 #. type: Content of: <chapter><section><section><para>
277 "Choose what you want to translate, make sure that nobody is already working "
278 "on it (using your debian-l10n-XXX mailing list), translate it, get it "
279 "reviewed by other native speakers on your l10n mailing list, and provide it "
280 "to the maintainer of the package (see next point)."
283 #. type: Content of: <chapter><section><section><title>
285 msgid "How to provide a translation for inclusion in a package"
288 #. type: Content of: <chapter><section><section><para>
291 "Make sure your translation is correct (asking for review on your l10n "
292 "mailing list) before providing it for inclusion. It will save time for "
293 "everyone, and avoid the chaos resulting in having several versions of the "
294 "same document in bug reports."
297 #. type: Content of: <chapter><section><section><para>
300 "The best solution is to file a regular bug containing the translation "
301 "against the package. Make sure to use the 'PATCH' tag, and to not use a "
302 "severity higher than 'wishlist', since the lack of translation never "
303 "prevented a program from running."
306 #. type: Content of: <chapter><section><title>
308 msgid "Best current practice concerning l10n"
311 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
314 "As a maintainer, never edit the translations in any way (even to reformat "
315 "the layout) without asking on the corresponding l10n mailing list. You risk "
316 "for example breaking the encoding of the file by doing so. Moreover, what "
317 "you consider an error can be right (or even needed) in the given language."
320 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
323 "As a translator, if you find an error in the original text, make sure to "
324 "report it. Translators are often the most attentive readers of a given "
325 "text, and if they don't report the errors they find, nobody will."
328 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
331 "In any case, remember that the major issue with l10n is that it requires "
332 "several people to cooperate, and that it is very easy to start a flamewar "
333 "about small problems because of misunderstandings. So if you have problems "
334 "with your interlocutor, ask for help on the corresponding l10n mailing list, "
335 "on debian-i18n, or even on debian-devel (but beware, l10n discussions very "
336 "often become flamewars on that list :)"
339 #. type: Content of: <chapter><section><itemizedlist><listitem><para>
342 "In any case, cooperation can only be achieved with <emphasis "
343 "role=\"strong\">mutual respect</emphasis>."