ubuntu-translations-coordinators team mailing list archive

[Nicolas François <nicolas.francois@xxxxxxxxxxxxxxx>]

Hello,

On Wed, Jun 09, 2010 at 04:02:27PM +0800, Arne Goetje wrote:
> 
> CCʼing Ubuntu Translation Coordinators team, since Ubuntu is
> downstream of Debian and therefore it should be also in Ubuntuʼs
> interest that this stuff gets fixed.
> 
> On 06/08/2010 01:56 AM, Christian PERRIER wrote:
> >Quoting Arne Goetje (arne.goetje@xxxxxxxxxxxxx):
> >>Hi Christian,
> >
> >CC'ing debian-l10n-devel mailing list, that gathers all people
> >involved in the Debian i18n infrastructure and scripts.
> >
> >>
> >>I just stumbled upon this translation overview page:
> >>http://www.debian.org/international/l10n/po/
> >>
> >>The script which generates the page seems to need some improvement:
> >>  * it seems not to use the iso_639_3.xml file from the iso-codes
> >>package, since many language codes are marked as "Unknown language".
> >
> >
> >I'm not sure this is easy to achieve. Nicolas, any idea?
> >
> >>  * language codes with @ modifiers are not parsed correctly. The
> >>script should split the string at the @ and display it like this:
> >>ca@valencia Catalan (valencia).
> >
> >That can probably be fixed even though my personal opinion about this
> >ca@valencia "joke" is....let's say this politically correct...mitigated..:-)
> 
> Well, yes. ca@valencia is for political reasons. But other
> variations (@latin, @devanagari) do make sense.
> 
> >>  * some entries look bogus, e.g. vi_AR. There are no translations
> >>with that code, so it needs to be investigated where this code comes
> >>from.
> >
> >Certainly from some bogus package providing a vi_AR.po file.
> 
> Well, that bogus .po file seems to be completely empty then, since
> following such links leads to 0 translatable strings and no .po
> files listed. Probably we would need to add some debugging code in
> the script to tell us which package carries such crap.

Maybe I did not followed the discussion completely, can you provide the
link.
Sometimes, the reason for the existence is just that at some time a PO
file did exist in a package.

Best Regards,
-- 
Nekral