Bug#616340: Another way to build /intl/l10n/*/$lang (Was: Missing language code on http://www.debian.org/international/l10n/po-debconf/de)

[David Prévot <david@tilapin.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Le 03/03/2011 17:16, David Prévot a écrit :
> Le 03/03/2011 13:24, Helge Kreutzmann a écrit :
>> Package: www.debian.org

> And for every subpage relative to language code, use the (full) language
> name [0] (with a fall back to language code if the language name is not
> defined).
> 
> With Helge example page [1], the breadcrumbs would “simply” be:
> 
>> Debian International / Zentrale Übersetzungsstatistik von Debian / PO Debconf / Deutsch

> or in English [2]:
> 
>> Debian International / Central Debian translation statistics / PO Debconf / German

	0: http://www.debian.org/international/l10n/po
	1: http://www.debian.org/international/l10n/po-debconf/de.de
	2: http://www.debian.org/international/l10n/po-debconf/de.en

Well, that's a bit more tricky that I'd have hopped. I fixed it to just
show the language code at the end (should be on-line tomorrow night in
Europe).

> BTW, I also noticed that there is no link to the translated pages in the
> bottom of those pages, I'll try to fix that in the process.

The current process to build those pages starts with a WML template,
that is used to build an HTML template, which is then duplicated to
include data of every language using a shell script.

Another approach to fix the “full language name in breadcrumbs“ and
“link to the translated pages in the footer” would be to add the data
sooner in a WML file, and to build each HTML file from its own WML source.

I'm not sure to be clear, so let me try a simple ASCII graph:

*Current process*
                         translation data
                                 |
                                 v
WML template ---> HTML template ---> HTML files
    (35)              (35)             (6000)

*Proposed alternative*

        translation data
              |
              v
WML template ---> WML files ---> HTML files
    (35)           (6000)          (6000)

Before trying to achieve this, I would appreciate comments, given that
there are currently 35 templates, that are used to build almost 6000
HTML files.

The proposed alternative would add 6000 new WML files in the building
tree (not on CVS of course), representing around 500MB of storage (not a
real problem since 5GB are still available on wolkenstein), and will
also add 6000 building from WML source on a daily basis (that should
take around an hour since a full rebuild of ~33000 files takes a bit
more than 6 hours).

Regards

David

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJNcbsBAAoJELgqIXr9/gnyHi8QAJKbbAenhJjQtrQ+O7rjjNEB
1OFhq1b/q+udc0P4jMP4pUMTwgAQbrWDGZdKVl+ARUesrCnpzagc2InkwE06kFwe
eE07a9/sD3ozu3MPvmtrkpQKr514c3dOh+27/X4CoPG51UuBOnG6I2vDKOiHvTn7
nnaIm8ObHsBI0Nb6BgQZsrIkKgmfk30AiwXzv7hw9gol1mijDaoMvkDdBMebLhW8
5cVAuNZtaIZgpnxjMChDHWapAZHdnmHpl3WTc0Lm9Ozw8wbFwfDDcVyxFKUDyf/D
axHsMgK/PIlDTKhHCA8GKIhkgXHdiNDMsM9CNdIu1xWCLqpGmPTplH/DAnymKWW3
UUZBBJ+hcl+JyJE6+8XRzZOIJitfrKaig5zeW4qQT1lhKs1IrNEKcrBEZE1cT7DE
jnJ/gvGmlUYeaxhA57IKRd1nzNt+NXGZXIQGKIOnKNLGDsSYIhjo5U6kd6ihfsRM
zcIFWLA7t13A+Ph5Qi1T7hZlXqFqvUCLB4MWY82KNy8W1Somp6bDZzzN/AmlPQVq
a0+9D7jMQNygBAxYEE6dm87TTS5dKU2qJGAZdcFN4MKvG3x3KCmGZj66od7toE6l
Hy43ONa59IPFsuHAlNszqBGnT2AU7t/YmLJ6YP+QKqF+AhUM/tWwE2i1+PRD1+PX
kwZlHnl4L35OSqacnsGJ
=2rd3
-----END PGP SIGNATURE-----