Update the NMU rules with the 0-day NMU rule created by release managers

[developers-reference.git] / l10n.dbk

diff --git a/l10n.dbk b/l10n.dbk
index e87276dc1fbcb0032496afeca7d6fd4570bd9ae8..a089e64b2406f5a2c491de02a914e6ae6a493fff 100644 (file)
--- a/l10n.dbk
+++ b/l10n.dbk
@@ -15,7 +15,7 @@ programs, you should read most of this chapter.
 </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
@@ -45,12 +45,12 @@ task, and the process depends on the kind of text you want to see translated.
 <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.
@@ -60,23 +60,24 @@ 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="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>
@@ -89,7 +90,7 @@ same way as its program messages.
 </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>
@@ -106,7 +107,7 @@ your feedback, so that this document can be enhanced.
 <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>
@@ -207,7 +208,7 @@ from running.
 <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>