Mailing List Archive

Support open source code!


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: tlug: kterm/kinput2 conversion



From: jwb@example.com (Jim Breen)
Subject: tlug: kterm/kinput2 conversion
Date: Wed, 9 Sep 1998 14:00:43 -0500

> (I *can* use jserver/kinput2 fine  with yudit, so I'm quite sure they are
> both working. Well done there, Gaspar.))
> 
> - I can't initiate conversion with kterm. In the setup on our Ultrix
> system, and on my old slackware system, the startup keystrokes were
> "Ctrl"+"\", so I more or less expected them to be the default. All I can 
> find in the  documantation are enigmatic references to "Ctrl-Kanji"
> (Initially kterm complained about missing XMODIFIERS, so I set that up and
> and now it is quiet, but still no action.) I also followd the advice in the
> kinput2 man page and added an inputmethod line to the resources file.

This is my .Xresources


kterm*kanjiMode: euc
kterm*visualBell: true
kterm*VT100*Translations: #override \
        Shift<Key>space: begin-conversion(_JAPANESE_CONVERSION)
kterm*preeditType:   Separate,OverTheSpot,OffTheSpot,Root 
kterm*inputMethod: kinput2 
kterm*Foreground: green
kterm*Background: black


-----

One problem I had with Debian (another libc6 system) is that
the X resources in my home directory were not getting
read in. 

When I started X with "startx" I didn't realize this at first.  Then
I checked it with

 $ xrdb -merge ~/.Xresources

and got an error message.  I forgot how I fixed it, but it is something
you might want to check.  Are your resources actually getting 
initialized?  Once it is set up, the resources above will start 
conversion with Shift Space.   

The inability of kterm or rxvt to start conversion is a common
issue, so there are a lot of other things to try.  I remember that
some programs using XIM, I think it was XEmacs, didn't start
conversion unless LANG was set to ja_JP.ujis or something like that
with

  $ export LANG=ja_JP.ujis

Maybe kterm is also affected by this?

Another thing to check is if both kterm and kinput2 are using
the same protocol.  

There are still a few other things to try if you still need ideas.


Regards,
Craig






--------------------------------------------------------------
Next Nomikai: 18 September, 19:30 Tengu TokyoEkiMae 03-3275-3691
Next Meeting: 10 October, Tokyo Station Yaesu central gate 12:30
--------------------------------------------------------------
Sponsor: PHT, makers of TurboLinux http://www.pht.co.jp


Home | Main Index | Thread Index

Home Page Mailing List Linux and Japan TLUG Members Links