|
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... > 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. 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]? [1] http://bugs.gentoo.org/show_bug.cgi?id=90476 [2] http://bugs.gentoo.org/attachment.cgi?id=97568 -- Bo Andresen |
pgpvoW0VQFZr8.pgp
Description: PGP signature
