Juliusz Chroboczek wrote:
> Wow. Could you please explain what's going on here?
In short: the mechanism which switches XLookupString to 'Latin1 only' mode
was broken.
X{mb|wc|utf8}LookupString calls XLookupString with this mode and then
deals with its output. The bug never appeared with non-multibyte encodings
becouse the X{mb|wc|utf8}LookupString family has a checking which discards
non-ascii char outputed by XLookupString if it is only one (becouse even
a Latin1 char is useless for X{mb|wc|utf8}LookupString which converts keysyms
to the char string in own way).
But under the UTF-8 locale XLookupString returns two (and more) chars
for non-ascii keysyms. And X{mb|wc|utf8}LookupString mistakely converted
them to UTF-8 one more time.
--
Ivan U. Pascal | e-mail: [EMAIL PROTECTED]
Administrator of | Tomsk State University
University Network | Tomsk, Russia
_______________________________________________
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n
