Ar an naoú lá is fiche de mí na Samhain, scríobh Zhang Wei:
> Use the Quail package (also known as LEIM). You can probably
> Tserver or Cserver of Wnn. Without a verbatim transcript of the
> messages, it's hard to say, but one possibility is that your input
> method is sending the Unicode extension keysyms to XEmacs, and we
> don't know how to handle that for Han characters AFAIK. (Aidan wrote
> the code so he would know better.) It would be best to wait for
> Unicode internal for that.
It's nothing to do with unicode, today I compiled xemacs-21.4 with
./configure --with-mule --with-xim=xlib --with-x11 \
--with-menubars=lucid --with-scrollbars=lucid --with-dialogs=athena \
--with-canna=no --with-wnn=no --with-xfs
and xemacs works with XIM chinese input method with no problem, but
compile 21.5 with the same configuration, the bug is still with
it. Now I am sure this bug is only for 21.5.
Okay, thank you for the information. You haven’t yet told us what the XXXX
is in the error message you’re describing, and I can neither get scim to do
anything useful--starts, doesn’t display anything--nor will xcin, a Chinese
input method that’s supported by my platform’s packaging system, pass text
to XEmacs, though it will to GTK2 apps. At the moment, I’m trying to get uim
I AM IN JAIL AND ALLOWED SEND ONLY ONE CABLE SINCE WAS ARRESTED WHILE
MEASURING FIFTEEN FOOT WALL OUTSIDE PALACE AND HAVE JUST FINISHED COUNTING
THIRTY EIGHT THOUSAND FIVE HUNDERED TWENTY TWO NAMES WHOS WHO IN MIDEAST.