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

Re: And now for something completely different... etch!

* Roger Leigh 

| Tollef Fog Heen <tfheen@err.no> writes:
| > * Roger Leigh 
| >
| > | - When UTF-8 is the default locale, it shouldn't need a .UTF-8 suffix,
| > |   e.g. en_GB will be UTF-8, and en_GB.ISO-8859-1 will be Latin-1 (the
| > |   opposite way round to the current situation which creates
| > |   en_GB.UTF-8 and en_GB [Latin-1]).
| >
| > Eh?  You can't change that around just like that, it will break in the
| > cases where people ssh in from machines with latin1 locales for
| > instance (and use the PassEnv feature of newer SSHs).
| IMHO if you want features like that to work, you should be fully
| qualifying your locale.  en_GB on its own has always meant "British
| English", in whatever locale the system administrator set as the
| default, and the same applies to all unqualified locales.

No, it haven't.  Read /usr/share/i18n/SUPPORTED which is what locales
are supported in what locale from glibc.

| I've used UTF-8 default locales for several years now, i.e.
| [/etc/locale.gen]
| en_GB UTF-8

That gives you undefined behaviour which may or may not work (by

Tollef Fog Heen                                                        ,''`.
UNIX is user friendly, it's just picky about who its friends are      : :' :
                                                                      `. `' 

Reply to: