Thanks for answering.
On 10/6/06, Bo Ørsted Andresen <[EMAIL PROTECTED]> wrote:
On Friday 06 October 2006 13:29, Liviu Andronic wrote:
> I have a slight problem with defining a en_US.UTF-8 locale. I tried the
> Gentoo Official Documentation on Localization and Syste-wide
> UTF-8, but I cannot make actually having en_US.UTF-8. Here are some
> commands I ran:
>
> The locales I have (nothing changes even after I run the rest of the
> commands.
> localhost ~ # locale -a
> C
> en_US.utf8
> POSIX
Please note that here locale -a doesn't show en_US.UTF-8, but en_US.utf8 (case change and missing dash).
Furthermore, I wouldn't have written on this matter if I didn't have problems with an application. I use emelFM2 as file manager and it uses LC_* variables to determine the encoding to be used for file names (if not mistaking anything). Now, after having made changes to the locales (emelFM2 was using C locale before, including for it's configuration file), filenames containing peculiar characters (Cyrillic and others) are illisible in the filelist. Moreover, although in debugs emelFM2 determines correctly that LC_ALL indicates en_US.UTF-8, it falls back (I believe) to using C locale instead of the utf-8 one (reads from and saves to config-C instead of config-en_US.UTF-8).
> localhost ~ # localedef -i en_US -f UTF-8 en_US.UTF-8
localedef is not necessary. Use locale-gen instead.
> localhost ~ # locale-gen
> * Generating 1 locales (this might take a while)
> * (1/1) Generating en_US.UTF-8 ... [ ok ] * Generation complete
Which you did - with success.
> localhost ~ # locale -a
> C
> en_US.utf8
> POSIX
> localhost ~ # env | grep -i LC_
> LC_ALL=en_US.UTF-8
And your current locale obviously is en_US.UTF-8. So... congrats... everything
is fine. :)
Not quite. Please see comments above.
--
Bo Andresen
--
Liviu
