#: l10n.dbk:7 msgid "Internationalization and Translations" msgstr "国際化と翻訳" # type: Content of: <chapter><para> #. type: Content of: <chapter><para> #: l10n.dbk:9 msgid "" "Debian supports an ever-increasing number of natural languages. Even if you " "are a native English speaker and do not speak any other language, it is part " "of your duty as a maintainer to be aware of issues of internationalization " "(abbreviated i18n because there are 18 letters between the 'i' and the 'n' " "in internationalization). Therefore, even if you are ok with English-only " "programs, you should read most of this chapter." msgstr "" "Debian がサポートしている自然言語の数は未だ増え続けています。あなたが英語圏の" "ネイティブスピーカーで他の言語を話さないとしても、国際化の問題について注意を" "払うことはメンテナとしてのあなたの責務です (internationalization の 'i' と 'n' " "の間に 18 文字があるので i18n と略されます)。つまり、あなたが英語のみの" "プログラムを扱っていて問題がない場合であっても、この章の大部分を読んでおく必要" "があるということです。" # type: Content of: <chapter><para> #. type: Content of: <chapter><para> #: l10n.dbk:17 msgid "" "According to <ulink url=\"&url-i18n-intro;" "\">Introduction to i18n</ulink> from Tomohiro KUBOTA, I18N " "(internationalization) means modification of a software or related " "technologies so that a software can potentially handle multiple languages, " "customs, and so on in the world, while L10N (localization) means " "implementation of a specific language for an already internationalized " "software." msgstr "" "久保田智広さんによる <ulink url=\"&url-i18n-intro;" "\">Introduction to i18n</ulink> によると、I18N (internationalization) は" "ソフトウェアや関連する技術を調整し、ソフトウェアが複数の言語、習慣、その他世界の物事" "などを扱えるようにすることで、対して L10N (localization) は既に国際化されている" "ソフトウェアに対して特定の言語を実装することです。" # type: Content of: <chapter><para> #. type: Content of: <chapter><para> #: l10n.dbk:26 msgid "" "l10n and i18n are interconnected, but the difficulties related to each of " "them are very different. It's not really difficult to allow a program to " "change the language in which texts are displayed based on user settings, but " "it is very time consuming to actually translate these messages. On the " "other hand, setting the character encoding is trivial, but adapting the code " "to use several character encodings is a really hard problem." msgstr "" "l10n と i18n は関連していますが、それぞれ関連する難しさについては違います。" "プログラムをユーザの設定に応じて表示されるテキストの言語を変更するようにする" "のはあまり難しくはありませんが、実際にメッセージを翻訳するのはとても時間が" "かかります。一方、文字のエンコード設定は些細な事ですが、複数の文字エンコード" "を扱えるようなコードにするのはとても難しい問題です。" # type: Content of: <chapter><para> #. type: Content of: <chapter><para> #: l10n.dbk:34 msgid "" "Setting aside the i18n problems, where no general guideline can be given, " "there is actually no central infrastructure for l10n within Debian which " "could be compared to the buildd mechanism for porting. So most of the work " "has to be done manually." msgstr "" # type: Content of: <chapter><section><title> #. type: Content of: <chapter><section><title> #: l10n.dbk:40 msgid "How translations are handled within Debian" msgstr "どの様にして Debian では翻訳が取り扱われているか" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:42 msgid "" "Handling translation of the texts contained in a package is still a manual " "task, and the process depends on the kind of text you want to see translated." msgstr "" "パッケージに含まれている文章の翻訳の取扱いは未だ手動であり、作業は翻訳したもの" "をどの様に見せたいかに因ります。" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:46 msgid "" "For program messages, the gettext infrastructure is used most of the time. " "Most of the time, the translation is handled upstream within projects like " "the <ulink url=\"&url-l10n-tp;\">Free " "Translation Project</ulink>, the <ulink url=\"&url-l10n-gnome;" "\">Gnome translation Project</ulink> or the <ulink url=\"&url-l10n-kde;" "\">KDE one</ulink>. The only centralized resource within " "Debian is the <ulink url=\"&url-l10n;\">Central " "Debian translation statistics</ulink>, where you can find some statistics " "about the translation files found in the actual packages, but no real " "infrastructure to ease the translation process." msgstr "" "プログラムのメッセージについては、ほとんどが gettext という仕組みが使われて" "います。多くの場合、翻訳は <ulink url=\"&url-l10n-tp;\">" "Free Translation Project</ulink> や <ulink url=\"&url-l10n-gnome;\">" "Gnome translation Project</ulink>、<ulink url=\"&url-l10n-kde;/\">KDE one</ulink> " "などの開発元 (upstream) のプロジェクトで取り扱われています。Debian で唯一の集約化" "された情報は <ulink url=\"&url-l10n;\">Debian の翻訳に関する統計</ulink>" "で、実際のパッケージ内での翻訳ファイルの状況について確認できますが、翻訳作業を実際に" "容易にする仕組みではありません。" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:59 msgid "" "An effort to translate the package descriptions started long ago, even if " "very little support is offered by the tools to actually use them (i.e., only " "APT can use them, when configured correctly). Maintainers don't need to do " "anything special to support translated package descriptions; translators " "should use the <ulink url=\"&url-ddtp;\">DDTP</ulink>." msgstr "" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:66 msgid "" "For debconf templates, maintainers should use the po-debconf package to ease " "the work of translators, who could use the DDTP to do their work (but the " "French and Brazilian teams don't). Some statistics can be found both on the " "DDTP site (about what is actually translated), and on the <ulink url=" "\"http://&www-debian-org;/intl/l10n/\">Central Debian translation " "statistics</ulink> site (about what is integrated in the packages)." msgstr "" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:74 msgid "" "For web pages, each l10n team has access to the relevant VCS, and the " "statistics are available from the Central Debian translation statistics site." msgstr "" "ウェブページについては、それぞれの l10n チームが対応する VCS にアクセスし、" "Debian の翻訳に関する統計サイトから統計情報が取得できます。" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:78 msgid "" "For general documentation about Debian, the process is more or less the same " "as for the web pages (the translators have access to the VCS), but there are " "no statistics pages." msgstr "" "Debian についての一般的なドキュメントは、作業は多少の差はあれウェブページと" "同じです (翻訳者は VCS にアクセスします)。ですが、統計情報のページはありません。" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:83 #, fuzzy msgid "" "For package-specific documentation (man pages, info documents, other " "formats), almost everything remains to be done." msgstr "" "パッケージ固有のドキュメント (man ページ、info ドキュメントその他) は" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:87 msgid "" "Most notably, the KDE project handles translation of its documentation in " "the same way as its program messages." msgstr "" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:91 msgid "" "There is an effort to handle Debian-specific man pages within a <ulink url=" "\"&url-cvsweb;manpages/?cvsroot=debian-doc\">specific VCS repository</ulink>." msgstr "" "Debian 固有の man ページを <ulink url=\"&url-cvsweb;manpages/?cvsroot=debian-doc\">" "特定の VCS リポジトリ</ulink> で取り扱おうという動きもあります。" # type: Content of: <chapter><section><title> #. type: Content of: <chapter><section><title> #: l10n.dbk:98 msgid "I18N & L10N FAQ for maintainers" msgstr "メンテナへの I18N & L10N FAQ" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:100 msgid "" "This is a list of problems that maintainers may face concerning i18n and " "l10n. While reading this, keep in mind that there is no real consensus on " "these points within Debian, and that this is only advice. If you have a " "better idea for a given problem, or if you disagree on some points, feel " "free to provide your feedback, so that this document can be enhanced." msgstr "" # type: Content of: <chapter><section><section><title> #. type: Content of: <chapter><section><section><title> #: l10n.dbk:107 msgid "How to get a given text translated" msgstr "翻訳された文章を得るには" # type: Content of: <chapter><section><section><para> #. type: Content of: <chapter><section><section><para> #: l10n.dbk:109 msgid "" "To translate package descriptions or debconf templates, you have nothing to " "do; the DDTP infrastructure will dispatch the material to translate to " "volunteers with no need for interaction from your part." msgstr "" # type: Content of: <chapter><section><section><para> #. type: Content of: <chapter><section><section><para> #: l10n.dbk:114 msgid "" "For all other material (gettext files, man pages, or other documentation), " "the best solution is to put your text somewhere on the Internet, and ask on " "debian-i18n for a translation in different languages. Some translation team " "members are subscribed to this list, and they will take care of the " "translation and of the reviewing process. Once they are done, you will get " "your translated document from them in your mailbox." msgstr "" # type: Content of: <chapter><section><section><title> #. type: Content of: <chapter><section><section><title> #: l10n.dbk:124 msgid "How to get a given translation reviewed" msgstr "どの様にして提供された翻訳をレビューするか" # type: Content of: <chapter><section><section><para> #. type: Content of: <chapter><section><section><para> #: l10n.dbk:126 msgid "" "From time to time, individuals translate some texts in your package and will " "ask you for inclusion of the translation in the package. This can become " "problematic if you are not fluent in the given language. It is a good idea " "to send the document to the corresponding l10n mailing list, asking for a " "review. Once it has been done, you should feel more confident in the " "quality of the translation, and feel safe to include it in your package." msgstr "" # type: Content of: <chapter><section><section><title> #. type: Content of: <chapter><section><section><title> #: l10n.dbk:136 msgid "How to get a given translation updated" msgstr "どの様にして提供された翻訳を更新するか" # type: Content of: <chapter><section><section><para> #. type: Content of: <chapter><section><section><para> #: l10n.dbk:138 msgid "" "If you have some translations of a given text lying around, each time you " "update the original, you should ask the previous translator to update the " "translation with your new changes. Keep in mind that this task takes time; " "at least one week to get the update reviewed and all." msgstr "" # type: Content of: <chapter><section><section><para> #. type: Content of: <chapter><section><section><para> #: l10n.dbk:144 msgid "" "If the translator is unresponsive, you may ask for help on the corresponding " "l10n mailing list. If everything fails, don't forget to put a warning in " "the translated document, stating that the translation is somehow outdated, " "and that the reader should refer to the original document if possible." msgstr "" # type: Content of: <chapter><section><section><para> #. type: Content of: <chapter><section><section><para> #: l10n.dbk:150 msgid "" "Avoid removing a translation completely because it is outdated. Old " "documentation is often better than no documentation at all for non-English " "speakers." msgstr "" "古くなっているからといって翻訳を全て削除するのは避けてください。非英語圏の" "ユーザにとって何もドキュメントが無いよりは古いドキュメントがある方が有益で" "あることが往々にしてあります。" # type: Content of: <chapter><section><section><title> #. type: Content of: <chapter><section><section><title> #: l10n.dbk:157 msgid "How to handle a bug report concerning a translation" msgstr "どの様にして翻訳関連のバグ報告を取り扱うか" # type: Content of: <chapter><section><section><para> #. TODO: add the i18n tag to the bug? #. type: Content of: <chapter><section><section><para> #: l10n.dbk:159 msgid "" "The best solution may be to mark the bug as forwarded to upstream, and " "forward it to both the previous translator and his/her team (using the " "corresponding debian-l10n-XXX mailing list)." msgstr "" # type: Content of: <chapter><section><title> #. type: Content of: <chapter><section><title> #: l10n.dbk:169 msgid "I18N & L10N FAQ for translators" msgstr "翻訳者への I18N & L10N FAQ" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:171 msgid "" "While reading this, please keep in mind that there is no general procedure " "within Debian concerning these points, and that in any case, you should " "collaborate with your team and the package maintainer." msgstr "" # type: Content of: <chapter><section><section><title> #. type: Content of: <chapter><section><section><title> #: l10n.dbk:176 msgid "How to help the translation effort" msgstr "どの様にして翻訳作業を支援するか" # type: Content of: <chapter><section><section><para> #. type: Content of: <chapter><section><section><para> #: l10n.dbk:178 msgid "" "Choose what you want to translate, make sure that nobody is already working " "on it (using your debian-l10n-XXX mailing list), translate it, get it " "reviewed by other native speakers on your l10n mailing list, and provide it " "to the maintainer of the package (see next point)." msgstr "" # type: Content of: <chapter><section><section><title> #. type: Content of: <chapter><section><section><title> #: l10n.dbk:186 msgid "How to provide a translation for inclusion in a package" msgstr "どの様にして提供した翻訳をパッケージに含めてもらうか" # type: Content of: <chapter><section><section><para> #. type: Content of: <chapter><section><section><para> #: l10n.dbk:188 msgid "" "Make sure your translation is correct (asking for review on your l10n " "mailing list) before providing it for inclusion. It will save time for " "everyone, and avoid the chaos resulting in having several versions of the " "same document in bug reports." msgstr "" # type: Content of: <chapter><section><section><para> #. type: Content of: <chapter><section><section><para> #: l10n.dbk:194 msgid "" "The best solution is to file a regular bug containing the translation " "against the package. Make sure to use the 'PATCH' tag, and to not use a " "severity higher than 'wishlist', since the lack of translation never " "prevented a program from running." msgstr "" # type: Content of: <chapter><section><title> #. type: Content of: <chapter><section><title> #: l10n.dbk:204 msgid "Best current practice concerning l10n" msgstr "l10n に関する現状でのベストプラクティス" # type: Content of: <chapter><section><itemizedlist><listitem><para> #. type: Content of: <chapter><section><itemizedlist><listitem><para> #: l10n.dbk:208 msgid "" "As a maintainer, never edit the translations in any way (even to reformat " "the layout) without asking on the corresponding l10n mailing list. You risk " "for example breaksing the encoding of the file by doing so. Moreover, what " "you consider an error can be right (or even needed) in the given language." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> #. type: Content of: <chapter><section><itemizedlist><listitem><para> #: l10n.dbk:216 msgid "" "As a translator, if you find an error in the original text, make sure to " "report it. Translators are often the most attentive readers of a given " "text, and if they don't report the errors they find, nobody will." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> #. type: Content of: <chapter><section><itemizedlist><listitem><para> #: l10n.dbk:223 msgid "" "In any case, remember that the major issue with l10n is that it requires " "several people to cooperate, and that it is very easy to start a flamewar " "about small problems because of misunderstandings. So if you have problems " "with your interlocutor, ask for help on the corresponding l10n mailing list, " "on debian-i18n, or even on debian-devel (but beware, l10n discussions very " "often become flamewars on that list :)" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> #. type: Content of: <chapter><section><itemizedlist><listitem><para> #: l10n.dbk:233 msgid "" "In any case, cooperation can only be achieved with <emphasis role=\"strong" "\">mutual respect</emphasis>." msgstr ""

# Debian Developer's Reference (Japanese) # (C) Hideki Yamane (Debian-JP) , 2008-2010. # msgid "" msgstr "" "Project-Id-Version: developers-reference 3.4.4\n" "POT-Creation-Date: 2009-09-06 02:31+0900\n" "PO-Revision-Date: 2010-01-06 10:27+0900\n" "Last-Translator: Hideki Yamane (Debian-JP) \n" "Language-Team: Debian JP Project \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. type: Content of: #: l10n.dbk:7 msgid "Internationalization and Translations" msgstr "国際化と翻訳" # type: Content of: <chapter><para> #. type: Content of: <chapter><para> #: l10n.dbk:9 msgid "" "Debian supports an ever-increasing number of natural languages. Even if you " "are a native English speaker and do not speak any other language, it is part " "of your duty as a maintainer to be aware of issues of internationalization " "(abbreviated i18n because there are 18 letters between the 'i' and the 'n' " "in internationalization). Therefore, even if you are ok with English-only " "programs, you should read most of this chapter." msgstr "" "Debian がサポートしている自然言語の数は未だ増え続けています。あなたが英語圏の" "ネイティブスピーカーで他の言語を話さないとしても、国際化の問題について注意を" "払うことはメンテナとしてのあなたの責務です (internationalization の 'i' と 'n' " "の間に 18 文字があるので i18n と略されます)。つまり、あなたが英語のみの" "プログラムを扱っていて問題がない場合であっても、この章の大部分を読んでおく必要" "があるということです。" # type: Content of: <chapter><para> #. type: Content of: <chapter><para> #: l10n.dbk:17 msgid "" "According to <ulink url=\"&url-i18n-intro;" "\">Introduction to i18n</ulink> from Tomohiro KUBOTA, I18N " "(internationalization) means modification of a software or related " "technologies so that a software can potentially handle multiple languages, " "customs, and so on in the world, while L10N (localization) means " "implementation of a specific language for an already internationalized " "software." msgstr "" "久保田智広さんによる <ulink url=\"&url-i18n-intro;" "\">Introduction to i18n</ulink> によると、I18N (internationalization) は" "ソフトウェアや関連する技術を調整し、ソフトウェアが複数の言語、習慣、その他世界の物事" "などを扱えるようにすることで、対して L10N (localization) は既に国際化されている" "ソフトウェアに対して特定の言語を実装することです。" # type: Content of: <chapter><para> #. type: Content of: <chapter><para> #: l10n.dbk:26 msgid "" "l10n and i18n are interconnected, but the difficulties related to each of " "them are very different. It's not really difficult to allow a program to " "change the language in which texts are displayed based on user settings, but " "it is very time consuming to actually translate these messages. On the " "other hand, setting the character encoding is trivial, but adapting the code " "to use several character encodings is a really hard problem." msgstr "" "l10n と i18n は関連していますが、それぞれ関連する難しさについては違います。" "プログラムをユーザの設定に応じて表示されるテキストの言語を変更するようにする" "のはあまり難しくはありませんが、実際にメッセージを翻訳するのはとても時間が" "かかります。一方、文字のエンコード設定は些細な事ですが、複数の文字エンコード" "を扱えるようなコードにするのはとても難しい問題です。" # type: Content of: <chapter><para> #. type: Content of: <chapter><para> #: l10n.dbk:34 msgid "" "Setting aside the i18n problems, where no general guideline can be given, " "there is actually no central infrastructure for l10n within Debian which " "could be compared to the buildd mechanism for porting. So most of the work " "has to be done manually." msgstr "" # type: Content of: <chapter><section><title> #. type: Content of: <chapter><section><title> #: l10n.dbk:40 msgid "How translations are handled within Debian" msgstr "どの様にして Debian では翻訳が取り扱われているか" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:42 msgid "" "Handling translation of the texts contained in a package is still a manual " "task, and the process depends on the kind of text you want to see translated." msgstr "" "パッケージに含まれている文章の翻訳の取扱いは未だ手動であり、作業は翻訳したもの" "をどの様に見せたいかに因ります。" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:46 msgid "" "For program messages, the gettext infrastructure is used most of the time. " "Most of the time, the translation is handled upstream within projects like " "the <ulink url=\"&url-l10n-tp;\">Free " "Translation Project</ulink>, the <ulink url=\"&url-l10n-gnome;" "\">Gnome translation Project</ulink> or the <ulink url=\"&url-l10n-kde;" "\">KDE one</ulink>. The only centralized resource within " "Debian is the <ulink url=\"&url-l10n;\">Central " "Debian translation statistics</ulink>, where you can find some statistics " "about the translation files found in the actual packages, but no real " "infrastructure to ease the translation process." msgstr "" "プログラムのメッセージについては、ほとんどが gettext という仕組みが使われて" "います。多くの場合、翻訳は <ulink url=\"&url-l10n-tp;\">" "Free Translation Project</ulink> や <ulink url=\"&url-l10n-gnome;\">" "Gnome translation Project</ulink>、<ulink url=\"&url-l10n-kde;/\">KDE one</ulink> " "などの開発元 (upstream) のプロジェクトで取り扱われています。Debian で唯一の集約化" "された情報は <ulink url=\"&url-l10n;\">Debian の翻訳に関する統計</ulink>" "で、実際のパッケージ内での翻訳ファイルの状況について確認できますが、翻訳作業を実際に" "容易にする仕組みではありません。" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:59 msgid "" "An effort to translate the package descriptions started long ago, even if " "very little support is offered by the tools to actually use them (i.e., only " "APT can use them, when configured correctly). Maintainers don't need to do " "anything special to support translated package descriptions; translators " "should use the <ulink url=\"&url-ddtp;\">DDTP</ulink>." msgstr "" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:66 msgid "" "For debconf templates, maintainers should use the po-debconf package to ease " "the work of translators, who could use the DDTP to do their work (but the " "French and Brazilian teams don't). Some statistics can be found both on the " "DDTP site (about what is actually translated), and on the <ulink url=" "\"http://&www-debian-org;/intl/l10n/\">Central Debian translation " "statistics</ulink> site (about what is integrated in the packages)." msgstr "" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:74 msgid "" "For web pages, each l10n team has access to the relevant VCS, and the " "statistics are available from the Central Debian translation statistics site." msgstr "" "ウェブページについては、それぞれの l10n チームが対応する VCS にアクセスし、" "Debian の翻訳に関する統計サイトから統計情報が取得できます。" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:78 msgid "" "For general documentation about Debian, the process is more or less the same " "as for the web pages (the translators have access to the VCS), but there are " "no statistics pages." msgstr "" "Debian についての一般的なドキュメントは、作業は多少の差はあれウェブページと" "同じです (翻訳者は VCS にアクセスします)。ですが、統計情報のページはありません。" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:83 #, fuzzy msgid "" "For package-specific documentation (man pages, info documents, other " "formats), almost everything remains to be done." msgstr "" "パッケージ固有のドキュメント (man ページ、info ドキュメントその他) は" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:87 msgid "" "Most notably, the KDE project handles translation of its documentation in " "the same way as its program messages." msgstr "" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:91 msgid "" "There is an effort to handle Debian-specific man pages within a <ulink url=" "\"&url-cvsweb;manpages/?cvsroot=debian-doc\">specific VCS repository</ulink>." msgstr "" "Debian 固有の man ページを <ulink url=\"&url-cvsweb;manpages/?cvsroot=debian-doc\">" "特定の VCS リポジトリ</ulink> で取り扱おうという動きもあります。" # type: Content of: <chapter><section><title> #. type: Content of: <chapter><section><title> #: l10n.dbk:98 msgid "I18N & L10N FAQ for maintainers" msgstr "メンテナへの I18N & L10N FAQ" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:100 msgid "" "This is a list of problems that maintainers may face concerning i18n and " "l10n. While reading this, keep in mind that there is no real consensus on " "these points within Debian, and that this is only advice. If you have a " "better idea for a given problem, or if you disagree on some points, feel " "free to provide your feedback, so that this document can be enhanced." msgstr "" # type: Content of: <chapter><section><section><title> #. type: Content of: <chapter><section><section><title> #: l10n.dbk:107 msgid "How to get a given text translated" msgstr "翻訳された文章を得るには" # type: Content of: <chapter><section><section><para> #. type: Content of: <chapter><section><section><para> #: l10n.dbk:109 msgid "" "To translate package descriptions or debconf templates, you have nothing to " "do; the DDTP infrastructure will dispatch the material to translate to " "volunteers with no need for interaction from your part." msgstr "" # type: Content of: <chapter><section><section><para> #. type: Content of: <chapter><section><section><para> #: l10n.dbk:114 msgid "" "For all other material (gettext files, man pages, or other documentation), " "the best solution is to put your text somewhere on the Internet, and ask on " "debian-i18n for a translation in different languages. Some translation team " "members are subscribed to this list, and they will take care of the " "translation and of the reviewing process. Once they are done, you will get " "your translated document from them in your mailbox." msgstr "" # type: Content of: <chapter><section><section><title> #. type: Content of: <chapter><section><section><title> #: l10n.dbk:124 msgid "How to get a given translation reviewed" msgstr "どの様にして提供された翻訳をレビューするか" # type: Content of: <chapter><section><section><para> #. type: Content of: <chapter><section><section><para> #: l10n.dbk:126 msgid "" "From time to time, individuals translate some texts in your package and will " "ask you for inclusion of the translation in the package. This can become " "problematic if you are not fluent in the given language. It is a good idea " "to send the document to the corresponding l10n mailing list, asking for a " "review. Once it has been done, you should feel more confident in the " "quality of the translation, and feel safe to include it in your package." msgstr "" # type: Content of: <chapter><section><section><title> #. type: Content of: <chapter><section><section><title> #: l10n.dbk:136 msgid "How to get a given translation updated" msgstr "どの様にして提供された翻訳を更新するか" # type: Content of: <chapter><section><section><para> #. type: Content of: <chapter><section><section><para> #: l10n.dbk:138 msgid "" "If you have some translations of a given text lying around, each time you " "update the original, you should ask the previous translator to update the " "translation with your new changes. Keep in mind that this task takes time; " "at least one week to get the update reviewed and all." msgstr "" # type: Content of: <chapter><section><section><para> #. type: Content of: <chapter><section><section><para> #: l10n.dbk:144 msgid "" "If the translator is unresponsive, you may ask for help on the corresponding " "l10n mailing list. If everything fails, don't forget to put a warning in " "the translated document, stating that the translation is somehow outdated, " "and that the reader should refer to the original document if possible." msgstr "" # type: Content of: <chapter><section><section><para> #. type: Content of: <chapter><section><section><para> #: l10n.dbk:150 msgid "" "Avoid removing a translation completely because it is outdated. Old " "documentation is often better than no documentation at all for non-English " "speakers." msgstr "" "古くなっているからといって翻訳を全て削除するのは避けてください。非英語圏の" "ユーザにとって何もドキュメントが無いよりは古いドキュメントがある方が有益で" "あることが往々にしてあります。" # type: Content of: <chapter><section><section><title> #. type: Content of: <chapter><section><section><title> #: l10n.dbk:157 msgid "How to handle a bug report concerning a translation" msgstr "どの様にして翻訳関連のバグ報告を取り扱うか" # type: Content of: <chapter><section><section><para> #. TODO: add the i18n tag to the bug? #. type: Content of: <chapter><section><section><para> #: l10n.dbk:159 msgid "" "The best solution may be to mark the bug as forwarded to upstream, and " "forward it to both the previous translator and his/her team (using the " "corresponding debian-l10n-XXX mailing list)." msgstr "" # type: Content of: <chapter><section><title> #. type: Content of: <chapter><section><title> #: l10n.dbk:169 msgid "I18N & L10N FAQ for translators" msgstr "翻訳者への I18N & L10N FAQ" # type: Content of: <chapter><section><para> #. type: Content of: <chapter><section><para> #: l10n.dbk:171 msgid "" "While reading this, please keep in mind that there is no general procedure " "within Debian concerning these points, and that in any case, you should " "collaborate with your team and the package maintainer." msgstr "" # type: Content of: <chapter><section><section><title> #. type: Content of: <chapter><section><section><title> #: l10n.dbk:176 msgid "How to help the translation effort" msgstr "どの様にして翻訳作業を支援するか" # type: Content of: <chapter><section><section><para> #. type: Content of: <chapter><section><section><para> #: l10n.dbk:178 msgid "" "Choose what you want to translate, make sure that nobody is already working " "on it (using your debian-l10n-XXX mailing list), translate it, get it " "reviewed by other native speakers on your l10n mailing list, and provide it " "to the maintainer of the package (see next point)." msgstr "" # type: Content of: <chapter><section><section><title> #. type: Content of: <chapter><section><section><title> #: l10n.dbk:186 msgid "How to provide a translation for inclusion in a package" msgstr "どの様にして提供した翻訳をパッケージに含めてもらうか" # type: Content of: <chapter><section><section><para> #. type: Content of: <chapter><section><section><para> #: l10n.dbk:188 msgid "" "Make sure your translation is correct (asking for review on your l10n " "mailing list) before providing it for inclusion. It will save time for " "everyone, and avoid the chaos resulting in having several versions of the " "same document in bug reports." msgstr "" # type: Content of: <chapter><section><section><para> #. type: Content of: <chapter><section><section><para> #: l10n.dbk:194 msgid "" "The best solution is to file a regular bug containing the translation " "against the package. Make sure to use the 'PATCH' tag, and to not use a " "severity higher than 'wishlist', since the lack of translation never " "prevented a program from running." msgstr "" # type: Content of: <chapter><section><title> #. type: Content of: <chapter><section><title> #: l10n.dbk:204 msgid "Best current practice concerning l10n" msgstr "l10n に関する現状でのベストプラクティス" # type: Content of: <chapter><section><itemizedlist><listitem><para> #. type: Content of: <chapter><section><itemizedlist><listitem><para> #: l10n.dbk:208 msgid "" "As a maintainer, never edit the translations in any way (even to reformat " "the layout) without asking on the corresponding l10n mailing list. You risk " "for example breaksing the encoding of the file by doing so. Moreover, what " "you consider an error can be right (or even needed) in the given language." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> #. type: Content of: <chapter><section><itemizedlist><listitem><para> #: l10n.dbk:216 msgid "" "As a translator, if you find an error in the original text, make sure to " "report it. Translators are often the most attentive readers of a given " "text, and if they don't report the errors they find, nobody will." msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> #. type: Content of: <chapter><section><itemizedlist><listitem><para> #: l10n.dbk:223 msgid "" "In any case, remember that the major issue with l10n is that it requires " "several people to cooperate, and that it is very easy to start a flamewar " "about small problems because of misunderstandings. So if you have problems " "with your interlocutor, ask for help on the corresponding l10n mailing list, " "on debian-i18n, or even on debian-devel (but beware, l10n discussions very " "often become flamewars on that list :)" msgstr "" # type: Content of: <chapter><section><itemizedlist><listitem><para> #. type: Content of: <chapter><section><itemizedlist><listitem><para> #: l10n.dbk:233 msgid "" "In any case, cooperation can only be achieved with <emphasis role=\"strong" "\">mutual respect</emphasis>." msgstr ""