Bug#609373: release-notes: Please translate architecture names

[Osamu Aoki <osamu@debian.org>]

Hi,

If others agree on my approach, I can commit.

On Wed, Jan 12, 2011 at 12:12:21PM +0100, Julien Cristau wrote:
> tag 609373 help
> kthxbye
> I don't think I'll get to that unless I get a patch.  Being an xml and
> po4a newbie I wouldn't know where to start.

As I looked the source, simplest solution is to have language specific override
ENTITY definition file in each language specific directory.

Can translations add to fr/language.ent etc. with translated content of
the following.  If not needed like in English, just add an empty file.

<!-- proper nouns for architectures -->
<!ENTITY arch-title "<phrase arch='alpha'>Alpha</phrase><!--
                  --><phrase arch='amd64'>64-bit PC in French</phrase><!--
                  --><phrase arch='armel'>ARM EABI</phrase><!--
                  --><phrase arch='hppa'>PA-RISC</phrase><!--
                  --><phrase arch='i386'>32-bit PC in French</phrase><!--
                  --><phrase arch='ia64'>IA-64</phrase><!--
                  --><phrase arch='mips'>Mips</phrase><!--
                  --><phrase arch='mipsel'>Mipsel</phrase><!--
                  --><phrase arch='powerpc'>PowerPC</phrase><!--
                  --><phrase arch='sparc'>SPARC</phrase><!--
                  --><phrase arch='s390'>S/390</phrase>">

Then we can change en/upgrading.dbk from:

<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
  <!ENTITY % shareddata   SYSTEM "../release-notes.ent" > %shareddata;
]>

    to

<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
  <!ENTITY % languagedata SYSTEM "language.ent" > %languagedata;
  <!ENTITY % shareddata   SYSTEM "../release-notes.ent" > %shareddata;
]>

First declaration wins in XML.

Osamu

PS: I hope this build process can run multiple language builds in parallel
since this has no tricky ones like
     <![%lang-fr;[
     <!ENTITY full-title "Guide de référence pour Debian">
     <!ENTITY p-debian-reference "debian-reference-fr">
     ]]>
which may be problematic for parallel build.