[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [I18n]xterm(+luit) and XIM

TK> Now, XTerm-156 + luit-0.6 doesn't support XIM input.

Correct.  Luit doesn't speak X; it only speaks TTY.

Luit assumes that the tty expects UTF-8 for client output and
generates UTF-8 for keystrokes.  It functions symmetrically: it
converts application output from ISO 2022 or locale-dependent
encodings into UTF-8 for the tty, and keyboard input from the TTY from
UTF-8 into the locale's encoding.

It seems rather clear to me that UTF-8 XTerm should provide keyboard
input in UTF-8.

TK> When using XIM, strings are given using XmbLookupString()
TK> or XwcLookupString().  Of course XmbLookupString() returns
TK> strings in locale encoding and XwcLookupString() returns
TK> strings in wchar_t.

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.

Regards,

                                        Juliusz
-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/linux-utf8/