TK> I agree, though my opinion is that luit will be a part of XTerm or
TK> be distributed with XTerm and automatically invoked from XTerm.
I'm planning to include luit in the XFree86 tree, and modify XTerm to
have a resource that specifies whether luit should be invoked.
Whether to build luit and whether this resource is set is site policy
(or distribution policy... I hear you have some clout within Debian).
It is premature to discuss default values right now.
Whether Thomas choses to distribute luit with XTerm is up to him. I
have no objection (but not yet, of course: I don't want anyone to
redistribute luit before I've blessed it with a 1.0 version number).
(I am of course reserving the right to use minors higher than 9.)
TK> Thus, now it is clear that XIM support is not luit's responsibility
TK> but XTerm's one.
Yep.
>> You should use Xutf8LookupString in UTF-8 mode. Your code should be
>> wrapped within #if OPT_USE_UTF8_API, which will automatically be
>> undefined on platforms that don't support Xutf8LookupString.
TK> Then, how can I write in #else ~ #endif ?
Sorry, I expressed myself carelessly. OPT_USE_UTF8_API is always
defined, but its value may be 1 or 0.
#if OPT_USE_UTF8_API
...
#endif
See the selection handling code in button.c for some examples.
TK> it may be Xutf8LookupString()'s fault.
That's quite possible; perhaps Bruno can comment. I'll try to have a
look when I next have some time.
Juliusz
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
