On Thursday 27 November 2003 14:53, Adam Scriven wrote:
> On Thu, Nov 27, 2003 at 02:22:22PM +0900, Jason Stubbs wrote:
> > I'm running a 100% bilingual Japanese-English system and it wouldn't be
> > too hard to install other languages. I don't know about Korean console -
> > the fonts above look like MS fonts. For X support, check out
> > app-i18n/nabi. Once you've installed that it should be the same as
> > putting the following before you start your wm session:
> > export LC_CTYPE="ja_JP" # what ever is appropriate for korean
> > /usr/X11R6/bin/kinput2 -canna & # run the input engine in background
>
> Ok, I've got nabi installed. At the end it said:
> * You MUST add environment variable...
> *
> * export XMODIFIERS="@im=nabi"
> * export XIM_PROGRAM=/usr/bin/nabi // for /xinit.xinitrx.d/xinput
>
> so I did that, resourced my .cshrc, but the kinput2 command doesn't seem
> to exist. I tried qpkg, but it couldn't find it either.
kinput2 is a Japanese input engine. I meant to say "#run YOUR input engine in
backround" above.
> I did get ami to run, but I have no idea how to configure it for korean
> input on an english keyboard.
> *lol*
> It would be a LOT easier if I understood korean.
>
> > There's also a XINPUT (I think) environment variable that should be set.
> > I don't know why I don't have it set or why it's working without it set,
> > but have a look into that too. Let me know if you can't find anything
> > about it.
>
> I haven't gotten there yet. ;)
XINPUT was incorrect - XMODIFIERS is what I was talking about. I don't know
what the XIM_PROGRAM is. Maybe the input engine is run automatically if the
that environment variable is set.
It sounds like everything is set up correctly, so you should be able to do
some key sequence (depends on nabi) which will switch on Korean input. For
kinput2 the default is shift+space; for nabi it might be the same but you'd
have to check the documentation.
If it doesn't work, try running /usr/bin/nabi& before starting X.
Jason
--
[EMAIL PROTECTED] mailing list
