| 1 |
On Friday 06 October 2006 20:51, Liviu Andronic wrote: |
| 2 |
> Thanks for answering. |
| 3 |
|
| 4 |
Was a mistake by me that I replied to the wrong mail of yours.. ;) |
| 5 |
|
| 6 |
[SNIP] |
| 7 |
> Please note that here locale -a doesn't show en_US.UTF-8, but |
| 8 |
> en_US*.utf8 *(case |
| 9 |
> change and missing dash). |
| 10 |
|
| 11 |
That's expected. Not an error. |
| 12 |
|
| 13 |
> Furthermore, I wouldn't have written on this matter if I didn't have |
| 14 |
> problems with an application. |
| 15 |
|
| 16 |
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... |
| 17 |
|
| 18 |
> I use emelFM2 as file manager and it uses |
| 19 |
> LC_* variables to determine the encoding to be used for file names (if not |
| 20 |
> mistaking anything). Now, after having made changes to the locales (emelFM2 |
| 21 |
> was using C locale before, including for it's configuration file), |
| 22 |
> filenames containing peculiar characters (Cyrillic and others) are |
| 23 |
> illisible in the filelist. Moreover, although in debugs emelFM2 determines |
| 24 |
> correctly that LC_ALL indicates en_US.UTF-8, it falls back (I believe) to |
| 25 |
> using C locale instead of the utf-8 one (reads from and saves to config-C |
| 26 |
> instead of config-en_US.UTF-8). |
| 27 |
|
| 28 |
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]? |
| 29 |
|
| 30 |
[1] http://bugs.gentoo.org/show_bug.cgi?id=90476 |
| 31 |
[2] http://bugs.gentoo.org/attachment.cgi?id=97568 |
| 32 |
|
| 33 |
-- |
| 34 |
Bo Andresen |
Archives