>>>> "Kazz" == Kazuyuki IENAGA
<ienaga(a)jsys.co.jp> writes:
Kazz> "Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
sb> Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes in
sb> xemacs-beta(a)xemacs.org:
> >> I think --with-xfs should just go away.
Kazz> [ how to do that snipped]
> input-method-xlib.c. And --with-xfs should probably be renamed
> to --with-multilingual-menubar. Alternatively, you could just
> require --with-xim for the multilingual menubar.
Kazz> --with-bilingual-menubar is correct IMHO. Can we put
Kazz> multilingual characters on menubars at same time?
I haven't tried it, but I don't see why not as long as you use X
Compound Text encoding.
Kazz> What need to be done and Stephen has done maybe...
Kazz> * remove input-method-xfs.c.
Done.
Kazz> * make configure to use input-method-xlib.c either
Kazz> --with-xim=xlib or --with-bilingual-menubar.
Don't know how ...
Kazz> * put "#ifdef HAVE_XIM" to enable XIM in input-method-xlib.c.
Kazz> * get rid of "#ifndef XIM_XLIB ..." in input-method-xlib.c.
Done in part, but I don't trust the quick hacks I made, maybe next
week I'll have time to review and get it right.
Kazz> In anyway, I don't want to use X input method, but just want
Kazz> to have bi-lingual menubar. For me, XIM is evil enough
Kazz> though...
Yes. I don't know; perhaps the locale stuff that XFontSet needs
should be separated into a separate file that --with-xim=xlib depends
on as well as input-method-xlib.c.
But I think that what needs to be done in any case is to make XIM
enabled on-the-fly as kterm does, and use the LEIM interface (C-u C-\,
etc) to invoke it.
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
__________________________________________________________________________
__________________________________________________________________________
What are those two straight lines for? "Free software rules."