Re: LC_ALL

[Roozbeh Pournader <roozbeh farsiweb info>]

On Tue, 2005-08-16 at 16:49 +0430, Roozbeh Pournader wrote:
> Perhaps we should have an environment variable for these, or one for
> each. Perhaps one could set LOCALE to
> "collation=phonebook,currency=DDM"?

Hmm, or should they use

LC_COLLATE=de_DE phonebook
LC_MONETARY=de_DE DDM

instead, but with enough logic to parse the part after the at sign, not
use it as a file name?

>From what I see from CLDR's key/types, collation can go into LC_COLLATE,
calendar can go into LC_TIME, currency into LC_MONETARY, and timezone to
some already-existing environment variable (Is it TZ?).

For non-deprecated variants, we have everything defined in RFC 3066:

http://www.evertype.com/standards/iso639/iana-lang-assignments.html

and then we have REVISED (for revised orthographies, whatever that
means) and SAAHO (a variant of Afar language) which we can put over
LC_MESSAGES.

But again, do we want the user to be able to "set it all" through an
LC_ALL?

roozbeh