Re: gtk bug or glibc locale bug?



Owen Taylor <otaylor@redhat.com> writes:

> > Why does the current code set gtk_use_mb value by "C" locale, not by
> > current locale?  I think it is a bug to be fixed.
> 
> The question isn't whether the C library handle multi-byte locales,
> the question is whether it will, for single byte locales, correctly
> report a length of 1. 
> 
> GTK+ is currently completely innocent of all knowledge of what
> locales are single-byte or multi-byte, so all it can do
> is check in the one locale that it knows is single-byte, the
> "C" locale. 

Yes, I really begin to understand.  The `\xc0' check is needed to keep
1-byte locales from wrong mb* functions..

I should contact with wcsmbs author, or release a modified GTK+.  And
wait the future GTK+, or glibc.  :-)

BTW, why not take \xc0 test in compile time?



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]