X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;ds=sidebyside;f=l10n.dbk;h=92bf3b99ba40c7c4b9bc89ea27d37cf02e423a09;hb=4b575d5020486873569980c2e7d673fa3a60fcbc;hp=dec77c462750511fb1bd6c1c400f52b34938ab49;hpb=24edeec3ea3aef827fc6c23b59bafec1f5343593;p=developers-reference.git

diff --git a/l10n.dbk b/l10n.dbk
index dec77c4..92bf3b9 100644
--- a/l10n.dbk
+++ b/l10n.dbk
@@ -1,6 +1,8 @@
 <?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">
+    "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+  <!ENTITY % commondata SYSTEM "common.ent" > %commondata;
+]>
 <chapter id="l10n">
 <title>Internationalizing, translating, being internationalized and being translated</title>
 <para>
@@ -13,10 +15,10 @@ 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="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.  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>
@@ -31,7 +33,7 @@ character encodings is a really hard problem.
 <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">
@@ -48,7 +50,7 @@ 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
 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.
@@ -65,7 +67,7 @@ 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).
 </para>
 <para>
@@ -87,7 +89,7 @@ same way as its program messages.
 </para>
 <para>
 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>.
 </para>
 </section>