[tlug] More on CentOS and Japanese input

[Scott Robbins <scottro@example.com>]

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

Ok, as it was a slow holiday type day, I installed CentOS. 

During installation, I chose to have Japanese support--I also installed
the various softeware development packages to be able to compile things.

This is what I found.

With kinput2 -canna, I could input Japanese in a uxterm, openoffice and
Evolution. 

XMODIFIERS="@example.com=kinput2"
LC_CTYPE=ja_JP.utf8

Note the lack of caps--doing locale -a | grep ja_JP showed me that this
is how CentOS does it, so it should be ut8, not UTF-8 or UTF8.  

Using en_US.utf8 enabled me to input Japanese in a uxterm but not in
openoffice--I didn't bother with evolution. 

With fluxbox, in such a situation, I add a script to call the
application with the proper variables, for example

XMODIFIERS="@example.com=kinput2" LC_CTYPE=ja_JP.utf8 ${1+"$@"} &

Then, I save the script as lang.sh and I would put in my fluxbox menu
for OpenOffice to call it with that shell.  In CentOS, the command (for
the writer) is oowriter, so there's probably a way to add that to the
menu, or else to simply open a terminal and do it.  

The scim anthy combo isn't available through CentOS repositories--I
don't know if they can use Fedora or not, and wasn't excited enough
about CentOS to start googling or looking through the docs. With the
developer tools installed, anthy, scim and scim-anthy all installed
without problem. 

I then killed cannaserver, set it, with ntsysv to not run on bootup, and
added the requisite lines to .bash_profile, as detailed in my howto.

problem.

However, when I tried to launch it with scim -d, it froze.

When I tried with scim -f socket -c socket -d it started, but I saw no
configuration options. 

So, I changed .bash_profile, for XMODIFIERS to be kinput2, used ntsysv
to allow canna to start at boot, and removed the GTK_IM_MODULE and
QT_IM_MODULE. 
I replaced scim -d with 

kinput2 -canna &

So, for the moment, I'm going to add a recommendation to my page that
CentOS users stick with kinput2-canna. 

Jim, if you have read this far, this ties in with your advice--you
suggested sticking with the default tools.  

As for openoffice, one definitely has to be sure that they've gone to
options=>tools=>languages and enabled Japanese. 

Leaving the LANG variable alone and having, in my .bash_profile,
LC_CTYPE=ja_JP.utf8, I was able to, with shift+space, input Japanese in
uxterm, openoffice and evolution.   (And, gnome-terminal for that
matter.)






- -- 

Scott Robbins

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

Buffy: Mom, dead people are talking to you. Do the math!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (FreeBSD)

iD8DBQFEqvkN+lTVdes0Z9YRAtKPAJ9kmSYAVrosG5ZaY+e5SW7WcmeYWACfUq9w
3DXElcu1dytt7IQzRufPBrc=
=gC4s
-----END PGP SIGNATURE-----