Comment 8 for bug 693337

Arne Goetje [2011-01-06 16:32 -0000]:
> What about /usr/share/locale/ ?

Good point, thanks, I missed that. I think we should offer

 - all languages/locales from /usr/share/langpack-locale/

plus

 - the intersection of /usr/share/locale/ and `locale -a`

Gunnar, how does that sound to you?

> >> * As regards languages with more than one translation: When the
> >> country is not specified, does it matter which of the locales that
> >> is assigned to the LC_MESSAGES environment variable?
> > No, it doesn't
> > for messages. It is relevant for $LANG and other LC_* categories, of
> > course.
>
> Why not? Falling back to en_GB for "English", while the rest of the LC_*
> and LANG is en_US, should surely be avoided.

en_US does specify a country, though. As we are always going to have
en_GB as an explicit variant, this case doesn't apply to English or
Portugese. I thought this was for the case if we only have "de"
translations, then the country in LC_MESSAGES doesn't matter.

> > I guess for the actual implementation in l-s and gdm we don't need
> > to parse /usr/share/xml/iso-codes/, as these already have the
> > translated names of the locales?
>
> hmm? l-s parses /usr/share/xml/iso-codes/ for exactly that reason.

Right, but it does that already, and gdm doesn't (it'd take too long
during boot). I was referring to Gunnar's perl script which currently
parses those.

Thanks,

Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)