Hi,
At Fri, 14 Dec 2001 18:45:13 +0100,
Juliusz Chroboczek wrote:
> XIM is intrinsically a locale-dependent protocol, as the set of
> available input methods is locale-dependent. Thus, the IM must be
> opened in the Input Method's locale.
Right.
> On the other hand, once the IM has been opened, its usage is fully
> locale-independent; conversion from the IM's codeset to UTF-8 is done
> internally by Xlib.
If you use Xutf8LookupString(), usage is locale-independent. (Instead,
it will dependent on a specific encoding of UTF-8.) If you use
XmbLookupString(), it will still give strings in encoding of the
locale when you opened the IM.
> In practice, what this means is that the user must set her locale
> according to the IM's she wishes to use. The programmer, on the other
> hand, does not need to bother with locale issues.
For standard softwares, this is right. ("Standard" means that the software
supplies a standard way for users to choose input methods.) On the
other hand, Yudit doesn't follow the standard way (users must configure
Yudit) and it should choose IM from its menu. It is Yudit's design.
To keep consistency with the design, Yudit should be able to choose
input methods from the menu. Concretely speaking, Yudit should have
"skkinput", "kinput2", "xcin (traditional Chinese)", "xcin (simplified
Chinese)", "ami", "htt", and so on. Of course I think the _initial_
input method can be chosen by following the standard configuration for
all XIM-supported softwares.
---
Tomohiro KUBOTA <[EMAIL PROTECTED]>
http://www.debian.or.jp/~kubota/
"Introduction to I18N" http://www.debian.org/doc/manuals/intro-i18n/
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
