Re: Re[6]: [M-Dev] Re: [M-CVS] CVS: M/src/gui wxFolderTree.cpp,1.239,1.240 wxFolderView.cpp,1.673,1.674

CC'ed to wx-dev to probably carry on there.

On Mon, 2006-02-13 at 01:32 +0100, Vadim Zeitlin wrote:
> On Sun, 12 Feb 2006 21:26:29 +0200 Mart Raudsepp <[email protected]> wrote:
> 
> MR> The problem might be, that you can't easily tell it to convert from your
> MR> certain encoding (say, KOI-8) to UTF-8, regardless of what the current
> MR> locale is.
> 
>  Indeed. So I have to set an UTF-8 locale. But then, as I wrote in my
> message to wx-dev, there doesn't seem to be any reason to not _always_ do
> it.

Is it always recognized?
For example, I specifically built my glibc only include support for
certain locales.
"locale -a" on my system outputs:
C
POSIX
en_US
en_US.utf8
et_EE

Although, all of et_EE.UTF-8, en_US.UTF-8 and en_US.utf8 do work without
giving a "locale not supported" warning.

However, en_US.utf8.UTF-8 does not work. Not sure how programmatically
"adding UTF-8" would work, and if this poses a problem related to the
fact that I can't do
LC_ALL=en_US.utf8.UTF-8 ./minimal
but I can do
LC_ALL=en_US.utf8 ./minimal


Also, I'm not sure if just adding utf-8 to the locale works with all
libc implementations.


> MR> Is there any other reason to use wxFontMapper?
> 
>  Well, under wxGTK2 which always supports UTF-8, no. wxFontMapper is mostly
> useful on non-Unicode systems (which were almost of them when Mahogany was
> started...).

Great that it should work now at least for some systems!
Hopefully back-porting so quickly, while already having a release
candidate, won't pose a problem.
I'm holding my back-ports for post 2.6.3, having unfortunately missed
the deadline. wxFontMapper backport should probably be fine, as it
didn't work at all before.

-- 
With regards,
Mart Raudsepp

Project manager of wxMUD
E-mail: [email protected]
http://wxmud.sourceforge.net/