ubuntu-translations-coordinators team mailing list archive
-
ubuntu-translations-coordinators team
-
Mailing list archive
-
Message #00094
Re: Understanding language packs
Adi Roiban wrote:
> Hi,
>
> I'm looking at the iso-codes template and the LP admin page [1]
> denote them as being part of language packs.
>
> Despite this, /usr/share/locale-langpack/ does not contain any iso*.mo
> files.
> The translations for iso-codes are rather distributed in the iso-codes
> binary package ($ dpkg -L iso-codes).
>
> iso-codes is in the "main" repository.
>
> How come that those files are not removed from the binary package?
>
> Why are they not included in the language packs, even when they are
> marked for inclusion?
>
> Many thanks for helping me understand all this :)!
>
> [1]
> https://translations.edge.launchpad.net/ubuntu/jaunty/+source/iso-codes/+pots/iso-639-3/+admin
iso-codes is a special case. The translations are needed by the
debian-installer/ubiquity and therefor before language-packs are even
available on the system. That's why the translations stay in the package.
Actually the translations in LP should not be exported into langpacks, I
have disable this for all the templates in Jaunty and Karmic now.
I also added a note in the description filed of each template, that
translations should be submitted back to upstream. Please feel free to
change the note, if you think the wording is not appropriate. ;)
For the iso-codes package I suggest to submit the translations back to
upstream way before feature freeze and ask upstream to release a new
version, so that we can get the final translations back into ubuntu
before feature freeze.
Cheers
Arne
Attachment:
signature.asc
Description: OpenPGP digital signature
References