> I believe the cause and effect was:
> 
>  - xcin didn't work
>  - This cause untested code to be run which crashed.

Hmm, let's go back my original question. :)
Why xcin work under XFree 4.1 but not under XFree 4.2 ?
I only wrote "setenv XMODIFIERS @im=xcin" into ~/.cshrc will cause
some programs (like gqview, mozilla,..etc) core dump without
stating up xcin. X-) xcin can be pop up but unusable.
After using your patch, I don't get core dump.
xcin still can be pop up but still unusable.

> So, the crash was a side effect of xcin not working; I looked
> at it a bit and it didn't work with:
> 
>  XMODIFIERS=@im=xcin
> 
> But it worked fine with:
> 
>  XMODIFIERS=@im=xcin-zh_TW
> 
> (At least, I got a status window to pop up.)

After setting "setenv LC_CTYPE zh_TW.Big5" on my system, I run xcin and
get this message:

XIM server) version 2.5.3-pre2.
(module ver: 20010918, syscin ver: 20000210).
(use "-h" option for help)

xcin: locale "zh_TW.Big5" encoding "big5"
xcin: XIM server "xcin" transport "X/"
                 ^^^^^^
xcin: inp_styles: Root OverTheSpot

So on my system, the XIM server name of xcin is "xcin".
After you starting xcin, you need to run a XIM client 
(like 'rxvt'or 'testprog') to try it.
If you push Shift+Ctrl keys and see the chinese words in the status window
be changed, it means xcin works correctly.

> If the previous used to work, it probably was because Xlib used to be
> less strict about checking the IM server name; xcin doesn't seem to
> support 'xcin' as a servername, just xcin-zh_TW and xcin-zh_CN.

So it seems to not a problem of XIM server name.

Regards,
-rxg
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert

Reply via email to