<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
- <!ENTITY % commondata SYSTEM "common.ent" > %commondata;
+ <!ENTITY % commondata SYSTEM "common.ent" > %commondata;
]>
<chapter id="l10n">
-<title>Internationalizing, translating, being internationalized and being translated</title>
+<title>Internationalization and Translations</title>
<para>
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
</para>
<para>
According to <ulink
-url="http://&www-debian-org;/doc/manuals/intro-i18n/">Introduction to
+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
+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.
</para>
<para>
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 has to be
+compared to the buildd mechanism for porting. So most of the work has to be
done manually.
</para>
<section id="l10n-handling">
<para>
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="http://www.iro.umontreal.ca/contrib/po/HTML/">Free Translation
+<ulink url="&url-l10n-tp;">Free Translation
Project</ulink>, the <ulink
-url="http://developer.gnome.org/projects/gtp/">Gnome translation
-Project</ulink> or the <ulink url="http://i18n.kde.org/">KDE one</ulink>. The
+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="http://&www-debian-org;/intl/l10n/">Central Debian translation
+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.
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="http://ddtp.debian.org/">DDTP</ulink>.
+<ulink url="&url-ddtp;">Debian Description Translation Project (DDTP)</ulink>.
</para>
<para>
-For debconf templates, maintainers should use the po-debconf package to ease
+For <systemitem role="package">debconf</systemitem> templates, maintainers
+should use the <systemitem role="package">po-debconf</systemitem> 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
+<ulink url="&url-ddtp;">DDTP site</ulink> (about what is actually translated),
+and on the <ulink url="&url-l10n;">Central Debian translation
statistics</ulink> site (about what is integrated in the packages).
</para>
<para>
-For web pages, each l10n team has access to the relevant CVS, and the
+For web pages, each l10n team has access to the relevant VCS, and the
statistics are available from the Central Debian translation statistics site.
</para>
<para>
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 no
+for the web pages (the translators have access to the VCS), but there are no
statistics pages.
</para>
<para>
</para>
<para>
There is an effort to handle Debian-specific man pages within a <ulink
-url="&url-cvsweb;manpages/?cvsroot=debian-doc">specific CVS
+url="&url-cvsweb;manpages/?cvsroot=debian-doc">specific VCS
repository</ulink>.
</para>
</section>
<section id="l10n-faqm-tr">
<title>How to get a given text translated</title>
<para>
-To translate package descriptions or debconf templates, you have nothing to do;
+To translate package descriptions or <systemitem role="package">debconf</systemitem> 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.
</para>
<title>How to handle a bug report concerning a translation</title>
<para>
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
+it to both the previous translator and their team (using the corresponding
debian-l10n-XXX mailing list).
<!-- TODO: add the i18n tag to the bug? -->
</para>
<para>
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
+example breaking the encoding of the file by doing so. Moreover, what you
consider an error can be right (or even needed) in the given language.
</para>
</listitem>
~ianmdlvl / developers-reference.git / blobdiff