Re: [gentoo-user] Re: problem getting UTF-8 locale

[Liviu Andronic]

Hello Bo

On 10/6/06, Bo Ørsted Andresen <bo.andresen@××××.dk> wrote:
>
> On Friday 06 October 2006 20:51, Liviu Andronic wrote:
>
> > Thanks for answering.
>
> Was a mistake by me that I replied to the wrong mail of yours.. ;)
>
> [SNIP]
>
> > Please note that here locale -a doesn't show en_US.UTF-8, but
>
> > en_US*.utf8 *(case
>
> > change and missing dash).
>
> That's expected. Not an error.
>
> > Furthermore, I wouldn't have written on this matter if I didn't have
>
> > problems with an application.
>
> Yes, but we aren't mind readers. Knowing that you probably had a reason
> that you decided wasn't worth mentioning really isn't helpful...
>
This was my mistake, to not have written all the problems.

> > 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).
>
> As you may have noticed emelfm2 has been removed from the portage tree
> because it lacks a maintainer.
>
Are you saying that it lacks a maintainer for keeping emelFM2 up-to-date in
portage? Since this is one good two-pane dependency-less file manager,
I cannot understand why
portage doesn't provide users with it. Is there any way to ask
portage devels to update regularly
emelFM2 ebuilds? (As it can be seen in [1], there are people providing
ebuilds for each emelFM2 release; couldn't they help maintaining emelFM2 in
portage?). I've tested it on Gentoo and it works in a pretty stable manner
(so that ~x86 would largely suffice for version 0.2).


The latest ebuild is on bug #90476 [1]. Unlike the latest ebuild in portage
> that actually has a unicode use flag. Did you use that one [2]?
>
I'm novice enough to Gentoo to not yet master emerging from custom ebuilds.
So I build it from source (make && make install). I used version 0.2.

However, the problem isn't emelFM2 specific. It is more linked to GTK+2
applications. For example, Qalculate! isn't able to display the pi sign (the
unicode pi sign). Or Xfce cannot display corefonts (Arial, Tahoma, Verdana).
Instead of displaying a unicode character (my guess), it displays
an incomprehensible series of numbers.

My guess is that it has to be somehow linked to locale, but I cannot see
how. I have a fresh 2006.1 Gentoo installation, with a customised kernel
having nls_utf8 built-in. The only crucial change that I made was upgrading
Xorg to 7.1. I generally build all my applications with +nls flag.


[1] http://bugs.gentoo.org/show_bug.cgi?id=90476
>
> [2] http://bugs.gentoo.org/attachment.cgi?id=97568
>
> --
>
> Bo Andresen
>
>


-- 
Liviu