Thanks for the fast bug fix. I hope, RedHat/Suse/etc. will fix this in
their RPMs *very soon*, otherwise the UTF-8 locales remain completely
unuseable for everyone on an X server without XKBD (e.g., Solaris).
Ivan Pascal wrote on 2002-11-29 12:46 UTC:
> 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.
Wasn't Xutf8LookupString supposed to be guaranteed to be locale
encoding *independent*? So why does it have to be implemented on top of
the (apparently) locale-dependent XLookupString? Sounds not entirely
kosher ...
> the X{mb|wc|utf8}LookupString family has a checking which discards
> non-ascii char outputed by XLookupString if it is only one
Why is it necessary to distinguish between ASCII and non-ASCII
characters?
> xc/lib/X11/XKB.c
Markus
--
Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK
Email: mkuhn at acm.org, WWW: <http://www.cl.cam.ac.uk/~mgk25/>
_______________________________________________
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n
