1 # Debian Developer's Reference (Japanese)
2 # (C) Hideki Yamane (Debian-JP) <henrich@debian.or.jp>, 2008.
6 "Project-Id-Version: developers-reference 3.4.1\n"
7 "POT-Creation-Date: 2008-06-14 23:00+0900\n"
8 "PO-Revision-Date: 2008-07-04 04:27+0900\n"
9 "Last-Translator: Hideki Yamane (Debian-JP) <henrich@debian.or.jp>\n"
10 "Language-Team: Debian JP Project <debian-doc@debian.or.jp>\n"
12 "Content-Type: text/plain; charset=UTF-8\n"
13 "Content-Transfer-Encoding: 8bit\n"
15 # type: Content of: <chapter><title>
18 "Internationalizing, translating, being internationalized and being translated"
20 "国際化、翻訳、国際化されること、翻訳されること"
22 # type: Content of: <chapter><para>
25 "Debian supports an ever-increasing number of natural languages. Even if you "
26 "are a native English speaker and do not speak any other language, it is part "
27 "of your duty as a maintainer to be aware of issues of internationalization "
28 "(abbreviated i18n because there are 18 letters between the 'i' and the 'n' "
29 "in internationalization). Therefore, even if you are ok with English-only "
30 "programs, you should read most of this chapter."
33 # type: Content of: <chapter><para>
36 "According to <ulink url=\"http://&www-debian-org;/doc/manuals/intro-i18n/"
37 "\">Introduction to i18n</ulink> from Tomohiro KUBOTA, I18N "
38 "(internationalization) means modification of a software or related "
39 "technologies so that a software can potentially handle multiple languages, "
40 "customs, and so on in the world, while L10N (localization) means "
41 "implementation of a specific language for an already internationalized "
45 # type: Content of: <chapter><para>
48 "l10n and i18n are interconnected, but the difficulties related to each of "
49 "them are very different. It's not really difficult to allow a program to "
50 "change the language in which texts are displayed based on user settings, but "
51 "it is very time consuming to actually translate these messages. On the "
52 "other hand, setting the character encoding is trivial, but adapting the code "
53 "to use several character encodings is a really hard problem."
56 # type: Content of: <chapter><para>
59 "Setting aside the i18n problems, where no general guideline can be given, "
60 "there is actually no central infrastructure for l10n within Debian which "
61 "could be compared to the buildd mechanism for porting. So most of the work "
62 "has to be done manually."
65 # type: Content of: <chapter><section><title>
67 msgid "How translations are handled within Debian"
68 msgstr "どの様にして Debian では翻訳が取り扱われているか"
70 # type: Content of: <chapter><section><para>
73 "Handling translation of the texts contained in a package is still a manual "
74 "task, and the process depends on the kind of text you want to see translated."
77 # type: Content of: <chapter><section><para>
80 "For program messages, the gettext infrastructure is used most of the time. "
81 "Most of the time, the translation is handled upstream within projects like "
82 "the <ulink url=\"http://www.iro.umontreal.ca/contrib/po/HTML/\">Free "
83 "Translation Project</ulink>, the <ulink url=\"http://developer.gnome.org/"
84 "projects/gtp/\">Gnome translation Project</ulink> or the <ulink url=\"http://"
85 "i18n.kde.org/\">KDE one</ulink>. The only centralized resource within "
86 "Debian is the <ulink url=\"http://&www-debian-org;/intl/l10n/\">Central "
87 "Debian translation statistics</ulink>, where you can find some statistics "
88 "about the translation files found in the actual packages, but no real "
89 "infrastructure to ease the translation process."
92 # type: Content of: <chapter><section><para>
95 "An effort to translate the package descriptions started long ago, even if "
96 "very little support is offered by the tools to actually use them (i.e., only "
97 "APT can use them, when configured correctly). Maintainers don't need to do "
98 "anything special to support translated package descriptions; translators "
99 "should use the <ulink url=\"http://ddtp.debian.org/\">DDTP</ulink>."
102 # type: Content of: <chapter><section><para>
105 "For debconf templates, maintainers should use the po-debconf package to ease "
106 "the work of translators, who could use the DDTP to do their work (but the "
107 "French and Brazilian teams don't). Some statistics can be found both on the "
108 "DDTP site (about what is actually translated), and on the <ulink url="
109 "\"http://&www-debian-org;/intl/l10n/\">Central Debian translation "
110 "statistics</ulink> site (about what is integrated in the packages)."
113 # type: Content of: <chapter><section><para>
116 "For web pages, each l10n team has access to the relevant CVS, and the "
117 "statistics are available from the Central Debian translation statistics site."
120 # type: Content of: <chapter><section><para>
123 "For general documentation about Debian, the process is more or less the same "
124 "as for the web pages (the translators have access to the CVS), but there are "
125 "no statistics pages."
128 # type: Content of: <chapter><section><para>
131 "For package-specific documentation (man pages, info documents, other "
132 "formats), almost everything remains to be done."
135 # type: Content of: <chapter><section><para>
138 "Most notably, the KDE project handles translation of its documentation in "
139 "the same way as its program messages."
142 # type: Content of: <chapter><section><para>
145 "There is an effort to handle Debian-specific man pages within a <ulink url="
146 "\"&url-cvsweb;manpages/?cvsroot=debian-doc\">specific CVS repository</ulink>."
149 # type: Content of: <chapter><section><title>
151 msgid "I18N & L10N FAQ for maintainers"
152 msgstr "メンテナへの I18N & L10N FAQ"
154 # type: Content of: <chapter><section><para>
157 "This is a list of problems that maintainers may face concerning i18n and "
158 "l10n. While reading this, keep in mind that there is no real consensus on "
159 "these points within Debian, and that this is only advice. If you have a "
160 "better idea for a given problem, or if you disagree on some points, feel "
161 "free to provide your feedback, so that this document can be enhanced."
164 # type: Content of: <chapter><section><section><title>
166 msgid "How to get a given text translated"
169 # type: Content of: <chapter><section><section><para>
172 "To translate package descriptions or debconf templates, you have nothing to "
173 "do; the DDTP infrastructure will dispatch the material to translate to "
174 "volunteers with no need for interaction from your part."
177 # type: Content of: <chapter><section><section><para>
180 "For all other material (gettext files, man pages, or other documentation), "
181 "the best solution is to put your text somewhere on the Internet, and ask on "
182 "debian-i18n for a translation in different languages. Some translation team "
183 "members are subscribed to this list, and they will take care of the "
184 "translation and of the reviewing process. Once they are done, you will get "
185 "your translated document from them in your mailbox."
188 # type: Content of: <chapter><section><section><title>
190 msgid "How to get a given translation reviewed"
191 msgstr "どの様にして提供された翻訳をレビューするか"
193 # type: Content of: <chapter><section><section><para>
196 "From time to time, individuals translate some texts in your package and will "
197 "ask you for inclusion of the translation in the package. This can become "
198 "problematic if you are not fluent in the given language. It is a good idea "
199 "to send the document to the corresponding l10n mailing list, asking for a "
200 "review. Once it has been done, you should feel more confident in the "
201 "quality of the translation, and feel safe to include it in your package."
204 # type: Content of: <chapter><section><section><title>
206 msgid "How to get a given translation updated"
207 msgstr "どの様にして提供された翻訳を更新するか"
209 # type: Content of: <chapter><section><section><para>
212 "If you have some translations of a given text lying around, each time you "
213 "update the original, you should ask the previous translator to update the "
214 "translation with your new changes. Keep in mind that this task takes time; "
215 "at least one week to get the update reviewed and all."
218 # type: Content of: <chapter><section><section><para>
221 "If the translator is unresponsive, you may ask for help on the corresponding "
222 "l10n mailing list. If everything fails, don't forget to put a warning in "
223 "the translated document, stating that the translation is somehow outdated, "
224 "and that the reader should refer to the original document if possible."
227 # type: Content of: <chapter><section><section><para>
230 "Avoid removing a translation completely because it is outdated. Old "
231 "documentation is often better than no documentation at all for non-English "
235 # type: Content of: <chapter><section><section><title>
237 msgid "How to handle a bug report concerning a translation"
238 msgstr "どの様にして翻訳関連のバグ報告を取り扱うか"
240 # type: Content of: <chapter><section><section><para>
241 #. TODO: add the i18n tag to the bug?
244 "The best solution may be to mark the bug as forwarded to upstream, and "
245 "forward it to both the previous translator and his/her team (using the "
246 "corresponding debian-l10n-XXX mailing list)."
249 # type: Content of: <chapter><section><title>
251 msgid "I18N & L10N FAQ for translators"
252 msgstr "翻訳者への I18N & L10N FAQ"
254 # type: Content of: <chapter><section><para>
257 "While reading this, please keep in mind that there is no general procedure "
258 "within Debian concerning these points, and that in any case, you should "
259 "collaborate with your team and the package maintainer."
262 # type: Content of: <chapter><section><section><title>
264 msgid "How to help the translation effort"
265 msgstr "どの様にして翻訳作業を支援するか"
267 # type: Content of: <chapter><section><section><para>
270 "Choose what you want to translate, make sure that nobody is already working "
271 "on it (using your debian-l10n-XXX mailing list), translate it, get it "
272 "reviewed by other native speakers on your l10n mailing list, and provide it "
273 "to the maintainer of the package (see next point)."
276 # type: Content of: <chapter><section><section><title>
278 msgid "How to provide a translation for inclusion in a package"
279 msgstr "どの様にして提供した翻訳をパッケージに含めてもらうか"
281 # type: Content of: <chapter><section><section><para>
284 "Make sure your translation is correct (asking for review on your l10n "
285 "mailing list) before providing it for inclusion. It will save time for "
286 "everyone, and avoid the chaos resulting in having several versions of the "
287 "same document in bug reports."
290 # type: Content of: <chapter><section><section><para>
293 "The best solution is to file a regular bug containing the translation "
294 "against the package. Make sure to use the 'PATCH' tag, and to not use a "
295 "severity higher than 'wishlist', since the lack of translation never "
296 "prevented a program from running."
299 # type: Content of: <chapter><section><title>
301 msgid "Best current practice concerning l10n"
302 msgstr "l10n に関する現状でのベストプラクティス"
304 # type: Content of: <chapter><section><itemizedlist><listitem><para>
307 "As a maintainer, never edit the translations in any way (even to reformat "
308 "the layout) without asking on the corresponding l10n mailing list. You risk "
309 "for example breaksing the encoding of the file by doing so. Moreover, what "
310 "you consider an error can be right (or even needed) in the given language."
313 # type: Content of: <chapter><section><itemizedlist><listitem><para>
316 "As a translator, if you find an error in the original text, make sure to "
317 "report it. Translators are often the most attentive readers of a given "
318 "text, and if they don't report the errors they find, nobody will."
321 # type: Content of: <chapter><section><itemizedlist><listitem><para>
324 "In any case, remember that the major issue with l10n is that it requires "
325 "several people to cooperate, and that it is very easy to start a flamewar "
326 "about small problems because of misunderstandings. So if you have problems "
327 "with your interlocutor, ask for help on the corresponding l10n mailing list, "
328 "on debian-i18n, or even on debian-devel (but beware, l10n discussions very "
329 "often become flamewars on that list :)"
332 # type: Content of: <chapter><section><itemizedlist><listitem><para>
335 "In any case, cooperation can only be achieved with <emphasis role=\"strong"
336 "\">mutual respect</emphasis>."