Bug#344048: installation-guide: Please make &debian; , and some other entities translatable

[Miroslav Kure <kurem@upcase.inf.upol.cz>]

On Tue, Dec 20, 2005 at 02:05:56AM +0900, Changwoo Ryu wrote:
> 
> But manual/build/entities/common.ent file defines &debian; entity as
> "Debian GNU/Linux" language independently, which makes the Korean
> translated manual very inconsistent.  
> 
> We need a way to translate these entities.

One really simple solution would be:

(This is probably the same as
 http://lists.debian.org/debian-boot/2004/12/msg00973.html but with
 real code attached :-))

cd manual
mkdir build/entities/l10n
for lang in ?? ??_??; do touch build/entities/l10n/${lang}.ent; done
rm build/entities/l10n/po.ent #not a language :-)
cd po
for lang in ?? ??_??; do touch ../build/entities/l10n/${lang}.ent; done

Add the following line to the build/templates/install.xml.template:
 <!ENTITY % dynamicdata    SYSTEM "../##TEMPDIR##/dynamic.ent"       > %dynamicdata;
+<!ENTITY % langdata       SYSTEM "##ENTPATH##/l10n/##LANG##.ent"       > %langdata;
 <!ENTITY % commondata     SYSTEM "##ENTPATH##/common.ent"        > %commondata;


Remarks:

 - each language would need its file in entities/l10n/
   (missing file will cause warning, but the build will go on)
   
 - when using different encoding from UTF-8, translators will need to
   specify it in their l10n/xx.ent file like they do in regular .xml
   files e.g. <?xml version="1.0" encoding="ISO-8859-2"?>
   
 - maybe we could prefill l10n/en.ent (or even all l10n/.ent files?)
   with some reasonable examples from common.ent

-- 
Miroslav Kure