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"
19 msgstr "国際化、翻訳、国際化されること、翻訳されること"
21 # type: Content of: <chapter><para>
24 "Debian supports an ever-increasing number of natural languages. Even if you "
25 "are a native English speaker and do not speak any other language, it is part "
26 "of your duty as a maintainer to be aware of issues of internationalization "
27 "(abbreviated i18n because there are 18 letters between the 'i' and the 'n' "
28 "in internationalization). Therefore, even if you are ok with English-only "
29 "programs, you should read most of this chapter."
32 # type: Content of: <chapter><para>
35 "According to <ulink url=\"http://&www-debian-org;/doc/manuals/intro-i18n/"
36 "\">Introduction to i18n</ulink> from Tomohiro KUBOTA, I18N "
37 "(internationalization) means modification of a software or related "
38 "technologies so that a software can potentially handle multiple languages, "
39 "customs, and so on in the world, while L10N (localization) means "
40 "implementation of a specific language for an already internationalized "
44 # type: Content of: <chapter><para>
47 "l10n and i18n are interconnected, but the difficulties related to each of "
48 "them are very different. It's not really difficult to allow a program to "
49 "change the language in which texts are displayed based on user settings, but "
50 "it is very time consuming to actually translate these messages. On the "
51 "other hand, setting the character encoding is trivial, but adapting the code "
52 "to use several character encodings is a really hard problem."
55 # type: Content of: <chapter><para>
58 "Setting aside the i18n problems, where no general guideline can be given, "
59 "there is actually no central infrastructure for l10n within Debian which "
60 "could be compared to the buildd mechanism for porting. So most of the work "
61 "has to be done manually."
64 # type: Content of: <chapter><section><title>
66 msgid "How translations are handled within Debian"
67 msgstr "どの様にして Debian では翻訳が取り扱われているか"
69 # type: Content of: <chapter><section><para>
72 "Handling translation of the texts contained in a package is still a manual "
73 "task, and the process depends on the kind of text you want to see translated."
76 # type: Content of: <chapter><section><para>
79 "For program messages, the gettext infrastructure is used most of the time. "
80 "Most of the time, the translation is handled upstream within projects like "
81 "the <ulink url=\"http://www.iro.umontreal.ca/contrib/po/HTML/\">Free "
82 "Translation Project</ulink>, the <ulink url=\"http://developer.gnome.org/"
83 "projects/gtp/\">Gnome translation Project</ulink> or the <ulink url=\"http://"
84 "i18n.kde.org/\">KDE one</ulink>. The only centralized resource within "
85 "Debian is the <ulink url=\"http://&www-debian-org;/intl/l10n/\">Central "
86 "Debian translation statistics</ulink>, where you can find some statistics "
87 "about the translation files found in the actual packages, but no real "
88 "infrastructure to ease the translation process."
91 # type: Content of: <chapter><section><para>
94 "An effort to translate the package descriptions started long ago, even if "
95 "very little support is offered by the tools to actually use them (i.e., only "
96 "APT can use them, when configured correctly). Maintainers don't need to do "
97 "anything special to support translated package descriptions; translators "
98 "should use the <ulink url=\"http://ddtp.debian.org/\">DDTP</ulink>."
101 # type: Content of: <chapter><section><para>
104 "For debconf templates, maintainers should use the po-debconf package to ease "
105 "the work of translators, who could use the DDTP to do their work (but the "
106 "French and Brazilian teams don't). Some statistics can be found both on the "
107 "DDTP site (about what is actually translated), and on the <ulink url="
108 "\"http://&www-debian-org;/intl/l10n/\">Central Debian translation "
109 "statistics</ulink> site (about what is integrated in the packages)."
112 # type: Content of: <chapter><section><para>
115 "For web pages, each l10n team has access to the relevant CVS, and the "
116 "statistics are available from the Central Debian translation statistics site."
119 # type: Content of: <chapter><section><para>
122 "For general documentation about Debian, the process is more or less the same "
123 "as for the web pages (the translators have access to the CVS), but there are "
124 "no statistics pages."
127 # type: Content of: <chapter><section><para>
130 "For package-specific documentation (man pages, info documents, other "
131 "formats), almost everything remains to be done."
134 # type: Content of: <chapter><section><para>
137 "Most notably, the KDE project handles translation of its documentation in "
138 "the same way as its program messages."
141 # type: Content of: <chapter><section><para>
144 "There is an effort to handle Debian-specific man pages within a <ulink url="
145 "\"&url-cvsweb;manpages/?cvsroot=debian-doc\">specific CVS repository</ulink>."
148 # type: Content of: <chapter><section><title>
150 msgid "I18N & L10N FAQ for maintainers"
151 msgstr "メンテナへの I18N & L10N FAQ"
153 # type: Content of: <chapter><section><para>
156 "This is a list of problems that maintainers may face concerning i18n and "
157 "l10n. While reading this, keep in mind that there is no real consensus on "
158 "these points within Debian, and that this is only advice. If you have a "
159 "better idea for a given problem, or if you disagree on some points, feel "
160 "free to provide your feedback, so that this document can be enhanced."
163 # type: Content of: <chapter><section><section><title>
165 msgid "How to get a given text translated"
168 # type: Content of: <chapter><section><section><para>
171 "To translate package descriptions or debconf templates, you have nothing to "
172 "do; the DDTP infrastructure will dispatch the material to translate to "
173 "volunteers with no need for interaction from your part."
176 # type: Content of: <chapter><section><section><para>
179 "For all other material (gettext files, man pages, or other documentation), "
180 "the best solution is to put your text somewhere on the Internet, and ask on "
181 "debian-i18n for a translation in different languages. Some translation team "
182 "members are subscribed to this list, and they will take care of the "
183 "translation and of the reviewing process. Once they are done, you will get "
184 "your translated document from them in your mailbox."
187 # type: Content of: <chapter><section><section><title>
189 msgid "How to get a given translation reviewed"
190 msgstr "どの様にして提供された翻訳をレビューするか"
192 # type: Content of: <chapter><section><section><para>
195 "From time to time, individuals translate some texts in your package and will "
196 "ask you for inclusion of the translation in the package. This can become "
197 "problematic if you are not fluent in the given language. It is a good idea "
198 "to send the document to the corresponding l10n mailing list, asking for a "
199 "review. Once it has been done, you should feel more confident in the "
200 "quality of the translation, and feel safe to include it in your package."
203 # type: Content of: <chapter><section><section><title>
205 msgid "How to get a given translation updated"
206 msgstr "どの様にして提供された翻訳を更新するか"
208 # type: Content of: <chapter><section><section><para>
211 "If you have some translations of a given text lying around, each time you "
212 "update the original, you should ask the previous translator to update the "
213 "translation with your new changes. Keep in mind that this task takes time; "
214 "at least one week to get the update reviewed and all."
217 # type: Content of: <chapter><section><section><para>
220 "If the translator is unresponsive, you may ask for help on the corresponding "
221 "l10n mailing list. If everything fails, don't forget to put a warning in "
222 "the translated document, stating that the translation is somehow outdated, "
223 "and that the reader should refer to the original document if possible."
226 # type: Content of: <chapter><section><section><para>
229 "Avoid removing a translation completely because it is outdated. Old "
230 "documentation is often better than no documentation at all for non-English "
234 # type: Content of: <chapter><section><section><title>
236 msgid "How to handle a bug report concerning a translation"
237 msgstr "どの様にして翻訳関連のバグ報告を取り扱うか"
239 # type: Content of: <chapter><section><section><para>
240 #. TODO: add the i18n tag to the bug?
243 "The best solution may be to mark the bug as forwarded to upstream, and "
244 "forward it to both the previous translator and his/her team (using the "
245 "corresponding debian-l10n-XXX mailing list)."
248 # type: Content of: <chapter><section><title>
250 msgid "I18N & L10N FAQ for translators"
251 msgstr "翻訳者への I18N & L10N FAQ"
253 # type: Content of: <chapter><section><para>
256 "While reading this, please keep in mind that there is no general procedure "
257 "within Debian concerning these points, and that in any case, you should "
258 "collaborate with your team and the package maintainer."
261 # type: Content of: <chapter><section><section><title>
263 msgid "How to help the translation effort"
264 msgstr "どの様にして翻訳作業を支援するか"
266 # type: Content of: <chapter><section><section><para>
269 "Choose what you want to translate, make sure that nobody is already working "
270 "on it (using your debian-l10n-XXX mailing list), translate it, get it "
271 "reviewed by other native speakers on your l10n mailing list, and provide it "
272 "to the maintainer of the package (see next point)."
275 # type: Content of: <chapter><section><section><title>
277 msgid "How to provide a translation for inclusion in a package"
278 msgstr "どの様にして提供した翻訳をパッケージに含めてもらうか"
280 # type: Content of: <chapter><section><section><para>
283 "Make sure your translation is correct (asking for review on your l10n "
284 "mailing list) before providing it for inclusion. It will save time for "
285 "everyone, and avoid the chaos resulting in having several versions of the "
286 "same document in bug reports."
289 # type: Content of: <chapter><section><section><para>
292 "The best solution is to file a regular bug containing the translation "
293 "against the package. Make sure to use the 'PATCH' tag, and to not use a "
294 "severity higher than 'wishlist', since the lack of translation never "
295 "prevented a program from running."
298 # type: Content of: <chapter><section><title>
300 msgid "Best current practice concerning l10n"
301 msgstr "l10n に関する現状でのベストプラクティス"
303 # type: Content of: <chapter><section><itemizedlist><listitem><para>
306 "As a maintainer, never edit the translations in any way (even to reformat "
307 "the layout) without asking on the corresponding l10n mailing list. You risk "
308 "for example breaksing the encoding of the file by doing so. Moreover, what "
309 "you consider an error can be right (or even needed) in the given language."
312 # type: Content of: <chapter><section><itemizedlist><listitem><para>
315 "As a translator, if you find an error in the original text, make sure to "
316 "report it. Translators are often the most attentive readers of a given "
317 "text, and if they don't report the errors they find, nobody will."
320 # type: Content of: <chapter><section><itemizedlist><listitem><para>
323 "In any case, remember that the major issue with l10n is that it requires "
324 "several people to cooperate, and that it is very easy to start a flamewar "
325 "about small problems because of misunderstandings. So if you have problems "
326 "with your interlocutor, ask for help on the corresponding l10n mailing list, "
327 "on debian-i18n, or even on debian-devel (but beware, l10n discussions very "
328 "often become flamewars on that list :)"
331 # type: Content of: <chapter><section><itemizedlist><listitem><para>
334 "In any case, cooperation can only be achieved with <emphasis role=\"strong"
335 "\">mutual respect</emphasis>."