# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
+# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
+#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-06-26 16:13+0000\n"
+"POT-Creation-Date: 2008-08-08 11:33-0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Content-Transfer-Encoding: ENCODING"
# type: Content of: <chapter><title>
-#: l10n.dbk:5
+#: l10n.dbk:7
msgid ""
"Internationalizing, translating, being internationalized and being "
"translated"
msgstr ""
# type: Content of: <chapter><para>
-#: l10n.dbk:7
+#: 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 "
msgstr ""
# type: Content of: <chapter><para>
-#: l10n.dbk:15
+#: l10n.dbk:17
msgid ""
"According to <ulink "
-"url=\"http://www.debian.org/doc/manuals/intro-i18n/\">Introduction to "
+"url=\"http://&www-debian-org;/doc/manuals/intro-i18n/\">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. "
+"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 ""
# type: Content of: <chapter><para>
-#: l10n.dbk:24
+#: 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 "
msgstr ""
# type: Content of: <chapter><para>
-#: l10n.dbk:32
+#: 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 dbuild mechanism for porting. So most of the work "
+"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>
-#: l10n.dbk:38
+#: l10n.dbk:40
msgid "How translations are handled within Debian"
msgstr ""
# type: Content of: <chapter><section><para>
-#: l10n.dbk:40
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><para>
-#: l10n.dbk:44
+#: 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 "
"url=\"http://developer.gnome.org/projects/gtp/\">Gnome translation "
"Project</ulink> or the <ulink url=\"http://i18n.kde.org/\">KDE one</ulink>. "
"The only centralized resource within Debian is the <ulink "
-"url=\"http://www.debian.org/intl/l10n/\">Central Debian translation "
+"url=\"http://&www-debian-org;/intl/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 ""
# type: Content of: <chapter><section><para>
-#: l10n.dbk:57
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><para>
-#: l10n.dbk:64
+#: 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 "
+"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>
-#: l10n.dbk:72
+#: l10n.dbk:74
msgid ""
"For web pages, each l10n team has access to the relevant CVS, and the "
"statistics are available from the Central Debian translation statistics "
msgstr ""
# type: Content of: <chapter><section><para>
-#: l10n.dbk:76
+#: 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 CVS), but there are "
msgstr ""
# type: Content of: <chapter><section><para>
-#: l10n.dbk:81
+#: l10n.dbk:83
msgid ""
"For package-specific documentation (man pages, info documents, other "
"formats), almost everything remains to be done."
msgstr ""
# type: Content of: <chapter><section><para>
-#: l10n.dbk:85
+#: 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>
-#: l10n.dbk:89
+#: l10n.dbk:91
msgid ""
"There is an effort to handle Debian-specific man pages within a <ulink "
-"url=\"http://cvs.debian.org/manpages/?cvsroot=debian-doc\">specific CVS "
+"url=\"&url-cvsweb;manpages/?cvsroot=debian-doc\">specific CVS "
"repository</ulink>."
msgstr ""
# type: Content of: <chapter><section><title>
-#: l10n.dbk:96
+#: l10n.dbk:98
msgid "I18N & L10N FAQ for maintainers"
msgstr ""
# type: Content of: <chapter><section><para>
-#: l10n.dbk:98
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: l10n.dbk:105
+#: l10n.dbk:107
msgid "How to get a given text translated"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: l10n.dbk:107
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: l10n.dbk:112
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: l10n.dbk:122
+#: l10n.dbk:124
msgid "How to get a given translation reviewed"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: l10n.dbk:124
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: l10n.dbk:134
+#: l10n.dbk:136
msgid "How to get a given translation updated"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: l10n.dbk:136
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: l10n.dbk:142
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: l10n.dbk:148
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: l10n.dbk:155
+#: l10n.dbk:157
msgid "How to handle a bug report concerning a translation"
msgstr ""
+#. TODO: add the i18n tag to the bug?
# type: Content of: <chapter><section><section><para>
-#: l10n.dbk:157
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><title>
-#: l10n.dbk:166
+#: l10n.dbk:169
msgid "I18N & L10N FAQ for translators"
msgstr ""
# type: Content of: <chapter><section><para>
-#: l10n.dbk:168
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: l10n.dbk:173
+#: l10n.dbk:176
msgid "How to help the translation effort"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: l10n.dbk:175
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: l10n.dbk:183
+#: l10n.dbk:186
msgid "How to provide a translation for inclusion in a package"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: l10n.dbk:185
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: l10n.dbk:191
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><title>
-#: l10n.dbk:201
+#: l10n.dbk:204
msgid "Best current practice concerning l10n"
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: l10n.dbk:205
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: l10n.dbk:213
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: l10n.dbk:220
+#: 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 "
msgstr ""
# type: Content of: <chapter><section><itemizedlist><listitem><para>
-#: l10n.dbk:230
+#: l10n.dbk:233
msgid ""
"In any case, cooperation can only be achieved with <emphasis "
"role=\"strong\">mutual respect</emphasis>."
~ianmdlvl / developers-reference.git / blobdiff