update .pot files

[developers-reference.git] / l10n.dbk

diff --git a/l10n.dbk b/l10n.dbk
index dd555864937067e91429c5c898fffbca244bc884..e87276dc1fbcb0032496afeca7d6fd4570bd9ae8 100644 (file)
--- a/l10n.dbk
+++ b/l10n.dbk
@@ -1,10 +1,10 @@
 <?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
@@ -18,7 +18,7 @@ According to <ulink
 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>
@@ -33,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">