Re: XIM, kinput2 & Tk

["Stephen J. Turnbull" <turnbull@example.com>]

>>>>> "Mike" == Mike Fabian <mfabian@example.com> writes:

    Mike> I think several applications look for LC_CTYPE to decide
    Mike> whether they should use XIM or not.

This is broken.  Locale in general is about external representations.
Try: info libc "chararcter set handling" "generic charset conversion"
to see the kinds of problems you get into if you use it for internal /
conversion purposes.

    Mike> Christopher SEKIYA <wileyc@example.com> writes:

    >> The keybindings are modified via Xdefaults, IIRC.

    Mike> For kinput2. For other XIM servers it may be different.
    Mike> nicolatter for example has the keybindings in it's own
    Mike> config files in ~/.nicolatter/ when it works together with
    Mike> Wnn, but uses the keybindings from ~/.canna if it works
    Mike> together with Canna.

Are you sure nicolatter is an XIM input manager?

If so, that is _even more disgusting_ than the hack I didn't describe
for kinput2.  X apps should never be dependent on host-local config
files, even the X Consortium eventually figured that out.

Sheesh, you might as well use Windows.  Why bother having a network
protocol at all if you're doing bondage with a single machine like
that?

-- 
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 straight lines for?  "XEmacs rules."