public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Liviu Andronic" <landronimirc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: problem getting UTF-8 locale
Date: Fri, 6 Oct 2006 20:51:24 +0200	[thread overview]
Message-ID: <68b1e2610610061151n2e390665x7dc1108245d23f67@mail.gmail.com> (raw)
In-Reply-To: <68b1e2610610060431r436b43bcw46ad254d3f942ecc@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1914 bytes --]

Thanks for answering.


On 10/6/06, Bo Ørsted Andresen <bo.andresen@zlin.dk> 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

[-- Attachment #2: Type: text/html, Size: 2684 bytes --]

  reply	other threads:[~2006-10-06 18:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06 11:31 [gentoo-user] problem getting UTF-8 locale Liviu Andronic
2006-10-06 18:51 ` Liviu Andronic [this message]
2006-10-06 19:29   ` [gentoo-user] " Bo Ørsted Andresen
2006-10-09 13:03     ` Liviu Andronic
2006-10-12  8:21       ` Bo Ørsted Andresen
2006-10-16  9:09         ` Liviu Andronic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=68b1e2610610061151n2e390665x7dc1108245d23f67@mail.gmail.com \
    --to=landronimirc@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox