On Sat, 2002-11-09 at 00:23, Andrew Bertola wrote: > On Thu, 2002-11-07 at 22:33, Thomas O'Dowd wrote: > > As for kinput2 not working. It works for me but of course it gets > > displayed as ____ when I convert something. Andrew, why are you killing > > kinput2 all the time. I start it once as lots of my apps use it. You > > might want to check that you have XMODIFIERS set. Something like... > > > > LANG=en_US LC_CTYPE=ja_JP LC_MESSAGES=en_US XMODIFIERS="@im=kinput2" > > evolution. > > No joy on RH 8.0. Maybe I have to take it up with them. It seems that > 1.0.8 worked w/ 7.3, but not with 8.0. I installed support for both > en_US and ja_JP. > > Then again, mutt works great with iso-2022-jp and kinput2 (at least > inside gnome-terminal w/ emacs -nw as editor). > > So, what's the difference in language support infrastructure?
No idea, I'm still using RH 7.1 and Gnome 1.4. No time to upgrade yet. Does Japanese input work within a normal kterm? Try starting a kterm and then echoing some kanji to the terminal. echo 'INPUTKANJIHERE'. If kinput works then it should also work with evolution. I don't use emacs but I think it has a slightly different way of handling things and talks directly to the canna servers. Make sure that XMODIFIERS is set. Also, how did you start kinput2? I use "kinput2 -canna". That still won't solve the display problems in evolution though. Larry, any further ideas on that? Cheers, Tom. -- Thomas O'Dowd, CEO, Nooper.com - Mobile Services Inc., Tokyo, Japan i-mode & FOMA consulting, development, testing: http://nooper.co.jp/ _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
