On Sat, May 07, 2005 at 12:32:28PM +0200, Nicolas Litchinko wrote:
> This one starts kinput2 with a connection to the canna server
> (canna.sh):
>
> #!/bin/bash
> export XMODIFIERS='@im=kinput2'
> export LANG=ja_JP.eucjp
> export LC_ALL=ja_JP.eucjp
> kinput2 -canna &
>
> And this one starts the application you want with kinput2 support
> (japan.sh):
>
> #!/bin/bash
> XMODIFIERS='@im=kinput2' [EMAIL PROTECTED] LANG=ja_JP.eucjp
> LC_ALL=ja_JP.eucjp ${1+"$@"} &
>
> (the last 2 lines are actually one long line)
Ooh! That's a nifty shell script. Right now I have two different
scripts to start rxvt and firefox with Japanese support, and two
others for Chinese support. It'd be nice for me to rewrite them all
into a meta script to launch with arbitrary LANG and XIM.
A thought: do you really need to export XMODIFIERS in canna.sh?
I have a file "kinput-start.sh"
#!/bin/bash
# Starts a Japanese Environment with valid SKK XIM
export LANG=ja_JP.eucJP
/usr/X11R6/bin/kinput2 &
unset LANG
which I load in my .xinitrc file along with a file "xcin-start.sh"
#!/bin/bash
# Starts a Chinese Environment with valid XCIN
export LANG=zh_TW
xcin &
unset LANG
And it seems to work fine as long as I include the export XMODIFIERS
in the script to launch the individual applications. I unset LANG
because I don't want to run _everything_ with a CJK environment, and
because those scripts are loaded before enlightenment in .xinitrc.
W
--
----------------------------------------------------------------
* Address: 45 Spelman Hall, Princeton University 08544 *
* Phone: x68958 AIM: AngularJerk *
* E-mail: [EMAIL PROTECTED] From: sep.dynalias.net *
----------------------------------------------------------------
"Those of you who are yawning are ok, but if you're terrified you should speak
up." ~DeathMech, S. Sondhi. P-town PHY 205
Sortir en Pantoufles: up 19 min
--
[email protected] mailing list
