Hi Marc,
At last, I have found a way to use UIM-XIM!
Here is what I did.
1) uim-xim &
=============screen=============
$ uim-xim
UIM-XIM bridge. Now supporting multiple locales.
Using full-synchronous XIM event flow
Supported conversion engines:
anthy (ja)
skk (ja)
ipa-x-sampa ()
latin ()
direct (*)
[EMAIL PROTECTED] registered, selecting skk (ja) as default conversion engine
=============screen=============
2) vim ~/.Xdefaults
=============screen=============
*inputMethod: uim
*preeditType: Root
*inputStyle: OldOverTheSpot
*international: true
*VT100.translations: #override \
Shift<Key>space: begin-conversion(_JAPANESE_CONVERSION)
=============screen=============
3) xrdb -merge ~/.Xdefaults
4) env [EMAIL PROTECTED] LANG=ja_JP.eucJP LC_CTYPE=ja_JP.eucJP xfig
-international
5) Click the "T" icon and push <Shift> + <Space>
6) Voila! You can input Japanese text there.
Thank you very much for porting UIM!
Now all I want is UIM-enabled mlterm in tree.
(I'm using mlterm-2.9.4pre [CVS HEAD].
The latest release is 2.9.3. Both are very stable.)
On 10/23/06, Marc Espie <[EMAIL PROTECTED]> wrote:
And I forgot: I haven't been able to make sense of the uim-xim bridge.
For that matter, I've never been able to use kinput2 either.
Someone who knows could send me a quick howto of things I need to tweak,
so that I'm at least able to try it out ?
xfig is probably the application where it makes the most sense...
--
tamo
