4:09 a.m.
I've checked out the latest cvs code, and built with:
./configure --with-mule --with-debug && make
But every chinese character that I input goes into the minibuffer
instead of the buffer, and caused a "xxxx not defined" error
message. There's no problem while inputing english.
Following is a copy of the "Installation" file generated after
configure.
---------------------------------------------------------------
uname -a: Linux debian 2.6.12-1-686 #1 Tue Sep 27 12:52:50 JST 2005 i686 GNU/Linux
./configure '--with-mule' '--with-debug'
XEmacs 21.5-b23 "daikon" (+CVS-20051127) configured for `i686-pc-linux'.
Compilation Environment and Installation Defaults:
Source code location: /home/zhangwei/emacs-study/xemacs-21.5
Installation prefix: /usr/local
Operating system description file: `s/linux.h'
Machine description file: `m/intel386.h'
Compiler version: gcc (GCC) 4.0.2 (Debian 4.0.2-2)
- GCC specs file: specs.
- Compiler command: gcc -Wall -Wno-switch -Wundef -Wsign-compare
-Wno-char-subscripts -Wpacked -Wunused-parameter -g
libc version: GNU libc 2.3.5-8 (Debian)
Relocating allocator for buffers: no
GNU version of malloc: yes
- Using Doug Lea's new malloc from the GNU C Library.
Window System:
Compiling in support for the X window system:
- X Windows headers location: /usr/X11R6/include
- X Windows libraries location: /usr/X11R6/lib
- Xau (X authority) not available.
- Handling WM_COMMAND properly.
Using Lucid menubars.
Using Lucid scrollbars.
TTY:
Compiling in support for ncurses.
Images:
Compiling in support for GIF images (builtin).
Compiling in support for XPM images.
Compiling in support for PNG images.
Compiling in support for JPEG images.
Compiling in support for TIFF images.
Sound:
Compiling in support for sound (native).
Compiling in support for NAS (network audio system).
Databases:
Internationalization:
Compiling in support for Mule (multi-lingual Emacs).
Compiling in support for XIM (X11R5+ I18N input method).
- Using raw Xlib to provide XIM support.
Mail:
Compiling in support for "file" mail spool file locking method.
Other Features:
Inhibiting IPv6 canonicalization at startup.
Compiling in support for dynamic shared object modules.
Using the new GC algorithms.
WARNING: ---------------------------------------------------------
WARNING: The new algorithms are experimental. They are enabled by
WARNING: default for this release. Use `--disable-kkcc' to
WARNING: turn it off.
WARNING: ---------------------------------------------------------
Using the new allocator.
WARNING: ---------------------------------------------------------
WARNING: The new allocator is experimental. It is enabled by
WARNING: default for this release. Use `--disable-mc-alloc' to
WARNING: turn it off.
WARNING: ---------------------------------------------------------
Using the new portable dumper.
Compiling in support for extra debugging code.
Compiling in support for runtime error checking.
WARNING: ---------------------------------------------------------
WARNING: XEmacs will run noticeably more slowly as a result.
WARNING: Error checking is on by default for XEmacs beta releases.
WARNING: ---------------------------------------------------------
2:05 p.m.
Thank you for the bug report!
Ar an t-ochtú lá is fiche de mí na Samhain, scríobh Zhang Wei:
I've checked out the latest cvs code, and built with:
./configure --with-mule --with-debug && make
But every chinese character that I input goes into the minibuffer
instead of the buffer, and caused a "xxxx not defined" error
message. There's no problem while inputing english.
How are you inputting Chinese? What’s the exact error message it gives you?
(I’m sure it doesn’t say xxxx, for example.) What’s your Xkb keyboard
layout, that is, what does setxkbmap -print give you? Do the XEmacs input
methods work? You can type C-u C-\ c h TAB to get a list of those.
--
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.
3:08 p.m.
>>>> "Zhang" == Zhang Wei
<id.brep(a)gmail.com> writes:
Zhang> But every chinese character that I input goes into the
Zhang> minibuffer instead of the buffer, and caused a "xxxx not
Zhang> defined" error message. There's no problem while inputing
Zhang> english.
Use the Quail package (also known as LEIM). You can probably also use
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.
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
3:48 p.m.
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
Use the Quail package (also known as LEIM). You can probably also
use
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 options:
./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.
10:12 p.m.
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
also use
> 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 options:
./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
working.
--
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.
7045
days inactive
7046
days old
4 comments
3 participants
participants (3)
-
Aidan Kehoe -
Stephen J. Turnbull -
Zhang Wei