Re: [tlug] Japanese Input on CentOS / KDE

[Scott Robbins <scottro@example.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, Aug 13, 2005 at 09:25:41PM +0900, Dave Gutteridge wrote:
> Scott,
> 
>     I think I have something here. A person on another list suggested that I place the following in 
> ~/.bash_profile:
> export XMODIFIERS='@example.com=kinput2'
> export LC_CTYPE=ja_JP.utf8
> /usr/X11R6/bin/kinput2 -canna &
> 
>     And it works great! With these settings in the .bash_profile file, I can even enter Japanese at 
> the prompt in a standard KDE konsole. It's available in pretty much every application I start.
> 

Ok, that answers two questions actually, will it work in .bash_profile
and will RH work with UTF-8.



>     The person who suggested this approach said that if I want this available for all users that I 
> should put these same lines of code into /etc/profile.d. But that same person also said that this 
> "might not be the best approach", although I'm not sure what his concern exactly is.


You're running kinput as soon as you boot in.  If people are using
console mode, it could confuse things. 


> 

>     I'm kind of curious to take that next step and make it a global setting for all users, but I 
> notice that you offer different suggestions as to what files should have the settings. I can see 
> that we're basically talking about the same three settings, but putting them in different places. 
> And I was wondering if there were advantages, disadvantages to them. If your way was better in some 
> way, I would conform to that.

The only issue I would have with it would be if you were logging into
console.   The other person's suggestion differs from mine in that he
said use utf8 while I said euc--however, this was just because we were
trying to get it working and I wasn't sure if RH worked with UTF-8, and
that he has kinput running from the moment you log in where I connected
to KDE. 

So, if you're sure you're not going to be switching over to a console
login, that way is fine. 


>     But at the very least, putting the settings as above is another thing you can add to advice for 
> users. It works like a charm for CentOS 4.1, and might be just as applicable to all builds of Red 
> Hat.


The revised (and probably somewhere in the morass of the current) has
the LC_CTYPE and XMODIFIER setttings in .bash_profile.  The starting of
kinput2 -canna, however, isn't something I'd put in profile. 

There are so many different ways of using it--remember one of your
earlier posts, when you said it seemed as if everyone had a different
way of doing it, adding to your confusion--that one has to try to be
general.   :)

There is a saying, that in Unix there is always more than one way to do
something.  The corollary is that someone is sure to think that your way
is wrong.   :)

- -- 

Scott Robbins

PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

Oz: It's Willow, she's nearby. 
Cordelia: What? You can smell her? She doesn't even wear perfume. 
Oz: She's afraid. 
Cordelia: Oh my God, is this some sort of residual werewolf 
thing? This is very disturbing. 
Oz: I really agree. 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iD8DBQFC/gcR+lTVdes0Z9YRAjRxAKC2sanbxZB+PrNMpRSfTN4SIgmquACeM9Qa
RIn2DtkBYWPbVAM2sGojnIc=
=gOyx
-----END PGP SIGNATURE-----