Re: [tlug] Japanese Input on CentOS / KDE

[Dave Gutteridge <dave@example.com>]

Scott,
    I followed your instructions as faithfully as I could. At first, I 
did not have kterm installed, so I had to hunt for an RPM. I got it 
though, and we're all good. At first I thought it was weird that the 
killall command found no process, when I had just seen a process with 
kinput2 in it. Then I realized that all that had been returned was a 
process to do with my search for kinput2, not an actual kinput2 process 
actually running.
    Anyway, here's how it went:

[root@example.com dave]# which kterm
/usr/X11R6/bin/kterm
[root@example.com dave]# ps ax | grep kinput2
 4196 pts/4    S+     0:00 grep kinput2
[root@example.com dave]# killall kinput2
kinput2: no process killed
[root@example.com dave]# kinput2 -canna &
[1] 4198
[root@example.com dave]# XMODIFIERS='@example.com=kinput2' LC_CTYPE=ja_JP.eucjp kterm

>Assuming we get that far, then please hit shift space and see if you get
>hiragana. 
>  
>
And I do!
I should point out something that is a small detail, but it threw me, 
and it could easily throw other newbies reading your new and improved 
web site.

When I first got into vi, I hit shift+space, and nothing happened. So my 
first impression was that we had not been successful in getting Japanese 
input.

But, to make a long story of experimentation short, what I discovered is 
that the very first time I press shift+space, I have to either hold it 
down for a second or two, or I have to rifle on the space key while 
holding down the shift key. In other words, it seems to take a moment or 
two to actually kick-start the Japanese input process. Maybe that's a 
loading from memory issue, or maybe my computer kind of sucks. In any 
case, it's a bit of a curve ball that might need mention, as it means 
one could potentially do everything right, and still not think they've 
got it set up.

But, the good news is that we have Japanese input, at least in vi, and 
if I set the environment before calling a kterm. I'm assuming (hoping?) 
there's a way to get this so that it's a global setting where I can have 
this available to all programs automatically, and not have to launch 
every application with this "XMODIFIERS..." stuff.

Dave