Re: [I18n]xterm and XIM

[hiura@xxxxxxxxxxx]

> From: Tomohiro KUBOTA <tkubota@xxxxxxxxxxx>
> > You mean, kinput2 and skkinput invoked something like
> >    LANG=ja_JP.eucJP kinput2 &
> >    LANG=ja_JP.UTF-8 XMODIFIERS=@im=kinput2 ./xterm -u8 &
> Yes.  I also tried
>     LANG=ja_JP.UTF-8 ./xterm -u8 -xrm "*inputMethod:kinput2"
> which gave the same result.

Oh, I see. 

> > Hmmm...if so, strange...
> 
> You mean, Kinput2 works well for you with XIM clients under UTF-8
> locales?  Then, Kinput2 is not responsible for this behavior...

I have not tried kinput2 recentry, but at least X11R5 days, it worked
if I remember correctly.

Since I use the IM Server "htt" since the day developing X11R5, and htt
has been evolved along with IM support in Xlib throughout
R5(Ximp)/R6(R6 XIM protocol)/post-R6(IIIM protocol), in my environment
both Xlib and htt support all of the protocols and there is no problem 
on EUC/UTF-8 combination. 

> > BTW, is Xlib capable of X11R6 XIM protocol only or X11R5 Ximp protocol
> > also enabled?
> 
> Since I have never used X11R5, I don't know how to check this.
> (When I started to use Linux, Ximp was already a historical protocol.)

This is FYI.

>From the first release of X11R6, the R6 Xlib is designed to support
both R5 XIM protocol(Ximp) and R6 XIM protocol through dynamic binding
mechanism. The code to enable R5 XIM protocol as well as R5 protocol
is placed in contrib as a patch to Xlib at that time. Therefore most
of commercial UNIXes support both R5 and R6 protocol.

X11R6.6 Xlib and the Xlib in li18nux.org CVS repository advanced this
binding mechanism as to load IM/OM/LC objects rather than linking them
in at compilation time, so that you can add/change/enhance I18N
capabilities without touching Xlib itself. 

For example, here is the loadable I18N objects externalized from Xlib
in my environment.

$ ls *.so.*
xiiimp.so.2      ximll.so.2       ximp40.so.2      xlibi18n.so.2
ximcp.so.2       ximlocal.so.2    xlcUTF-8.so.2    xomLTRTTB.so.2

> > If they still don't, would you kindly try with the latest Xlib in the
> > li18nux.org CVS repository, which is the full merger of
> > X11R6.6/XFree86 4.0.3/Solaris XI18N Xlib for XFree86 4.0.3 environment?
> I am using development (unstable) version of Debian, so called "Sid".
> It includes GNU libc 2.2.3 and XFree86 4.0.3 now.

The reason I asked you to try the one in li18nux.org CVS is that this
Xlib can naturally be the most *IM Rich* Xlib, since this is
maintained by whom designed those IM standards and used as a test bed,
so we may be able to step aside of the IM specification ambiguity if
any. Thus I thought it might be helpful to articurate the problem if
you can try with this Xlib, but there is another way, the otherway
around; With your current Xlib with my IM Server htt(also in
li18nux.org CVS). Htt uses CSD(CodeSet Dependent) approach by
hard-wiring to UTF-16 with additional attributes.
# (Why UTF-16 instead of UTF-8? UTC guys tend to choose UTF-16 ;-P) 
Htt supports all of those three IM protocols, and for Japanese free
engine support, the canna language engine interface comes with in the
CVS repository.

--
hiura@{sun.com,li18nux.org,kondara.org,unicode.org} http://www.li18nux.org
Chair, Li18nux/Linux Internationalization Initiative, Free Standards Group
Architect/Sr. Staff Engineer, Sun Microsystems, Inc, USA  FAX 650-786-9553
-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/linux-utf8/