Hi,
Now, XTerm-156 + luit-0.6 doesn't support XIM input.
How will XTerm + luit support XIM input?
When using XIM, strings are given using XmbLookupString()
or XwcLookupString(). Of course XmbLookupString() returns
strings in locale encoding and XwcLookupString() returns
strings in wchar_t. Either can be used. Note that XIM
does not give keysym, because more than one characters
can be given for one X{mb,wc}LookupString() invocation.
(A keysym can express only one character or key press.)
Which one should be used? We need strings in UTF-8 or UCS-4.
If we use XmbLookupString(), we have to convert the string
from locale encoding to UTF-8 or UCS-4. This can be achieved
using nl_langinfo(CODESET) and iconv() but participants of
this mailing list seem to dislike this approach. Yes, this
is not very portable. (This is why luit is introduced, isn't it?)
I don't know whether fontenc mechanism can be used for this
conversion or not.
If we use XwcLookupString(), if __STDC_ISO_10646__ is
available, it would be very easy but this will spoil
portability.
XTerm-152-27 supports XIM input using XmbLookupString() and
nl_langinfo(CODESET) and iconv().
I don't know whether luit can handle XIM input and convert
it into UCS keysym.
Any suggestions?
---
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/
