[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#552561: Bug#552560: locale selection incomplete



Christian Perrier a écrit :
> Quoting martin f krafft (madduck@debian.org):
>> also sprach Christian Perrier <bubulle@debian.org> [2009.10.28.0726 +0100]:
>>> - write an en_CH locale and convince glibc maintainers to include it
>>> in locales
>> You should know me better, Christian! #552561 ;)
> 
> I'm not sure I would support it strongly as it would open the gates
> for any kind of locales. 
> 
> It's probably hard to set a strong policy on locales and I don't
> exactly know the policy used by glibc upstream. It's quite probable
> that they decide to include a locale for a language_country
> combination when the said language has the status of official language
> in the said country (with an exception for regional languages where
> the policy is probably to create a locale when the said regional
> language is noticeably spoken as primary language y a significant part
> of the population).
> 
> It's hard to draw lines here, but I don't think that en_CH fits such criteria.
> otherwise we would end up with hundreds of en_FOO locales...
> 

I fully agree with that. The locale system on UNIX is well designed, so
you can select different value for the various locale categories.

In your case the following settings will probably match your use case:

LC_CTYPE="de_CH.UTF-8"
LC_NUMERIC="de_CH.UTF-8"
LC_TIME="de_CH.UTF-8"
LC_COLLATE="de_CH.UTF-8"
LC_MONETARY="de_CH.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER="de_CH.UTF-8"
LC_NAME="de_CH.UTF-8"
LC_ADDRESS="de_CH.UTF-8"
LC_TELEPHONE="de_CH.UTF-8"
LC_MEASUREMENT="de_CH.UTF-8"
LC_IDENTIFICATION="de_CH.UTF-8"

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net



Reply to: