Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: kterm/kinput2 conversion
- To: tlug@example.com
- Subject: Re: tlug: kterm/kinput2 conversion
- From: Craig Oda <craigoda@example.com>
- Date: Tue, 08 Sep 1998 23:03:24 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: Text/Plain; charset=us-ascii
- In-Reply-To: Your message of "Wed, 9 Sep 1998 14:00:43 -0500"<199809090400.OAA29442@example.com>
- References: <199809090400.OAA29442@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
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
- Follow-Ups:
- Re: tlug: kterm/kinput2 conversion
- From: "Eric S. Standlee" <fwiw3980@example.com>
- References:
- tlug: kterm/kinput2 conversion
- From: jwb@example.com (Jim Breen)
Home | Main Index | Thread Index
- Prev by Date: tlug: kterm/kinput2 conversion
- Next by Date: Re: Debian Install program [ was Re: tlug: CDRom Burner & Debian 2.0 distribution]
- Prev by thread: tlug: kterm/kinput2 conversion
- Next by thread: Re: tlug: kterm/kinput2 conversion
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links