CentOS - Aug 2005 - httx, iiimf, and Japanese input still not working

Japanese input - the final frontier. This is the last obstacle before I 
can work completely within Centos and be free of Windows.
But it's still not working.

To cut to the chase, in my quest to get Japanese working, I came across 
the following:
https://www.redhat.com/archives/fedora-i18n-list/2004-November/msg00030.html
... where someone says:
"You need to have httx (htt_xbe) running to use iiimf in KDE."

Okay, so I go looking on the net for httx, but can't quite figure out 
what it is or how to download it.

So my question is what is it, where do I get it, and will it help me get 
Japanese input?

Now, for anyone who needs a reference, what follows is how I came to 
find out about httx.

I was following the instructions on this page:
http://fedora.redhat.com/projects/i18n/iiimf-faq.html

And here are the results of some of the commands they suggest to check 
if iiimf is running in KDE:

[root at localhost dave]# service iiim status
htt (pid 3193) is running...

[root at localhost dave]# rpm -qa |grep iiimf
iiimf-csconv-12.1-13.EL
iiimf-protocol-lib-11.4-43
iiimf-libs-devel-12.1-13.EL
iiimf-libs-12.1-13.EL
iiimf-gtk-12.1-13.EL
iiimf-client-lib-11.4-43
iiimf-x-12.1-13.EL
iiimf-gnome-im-switcher-12.1-13.EL
iiimf-le-unit-12.1-13.EL
iiimf-client-lib-devel-11.4-43
iiimf-server-12.1-13.EL
iiimf-le-canna-12.1-13.EL
iiimf-docs-12.1-13.EL
iiimf-protocol-lib-devel-11.4-43

[root at localhost dave]# ps auxwww | grep httx
root      4433  0.0  0.2  5272  664 pts/4    S+   18:38   0:00 grep httx

[root at localhost dave]# LANG=ja_JP.UTF-8 XMODIFIERS=@im=htt kedit
QInputContext: no input method context available
QInputContext: no input method context available

When I went to Google to look up this error, that's when I eventually 
came across httx, but that's where I was stonewalled.

I hope someone can help me get this last piece of the puzzle in place.

Dave

On Sun, 2005-08-07 at 18:52 +0900, Dave Gutteridge
wrote:
> Japanese input - the final frontier. This is the last obstacle before I 
> can work completely within Centos and be free of Windows.
> But it's still not working.
> 
> To cut to the chase, in my quest to get Japanese working, I came across 
> the following:
>
https://www.redhat.com/archives/fedora-i18n-list/2004-November/msg00030.html
> ... where someone says:
> "You need to have httx (htt_xbe) running to use iiimf in KDE."
> 
> Okay, so I go looking on the net for httx, but can't quite figure out 
> what it is or how to download it.
> 
> So my question is what is it, where do I get it, and will it help me get 
> Japanese input?
> 
> Now, for anyone who needs a reference, what follows is how I came to 
> find out about httx.
> 
> I was following the instructions on this page:
> http://fedora.redhat.com/projects/i18n/iiimf-faq.html
> 
> And here are the results of some of the commands they suggest to check 
> if iiimf is running in KDE:
> 
> [root at localhost dave]# service iiim status
> htt (pid 3193) is running...
> 
> [root at localhost dave]# rpm -qa |grep iiimf
> iiimf-csconv-12.1-13.EL
> iiimf-protocol-lib-11.4-43
> iiimf-libs-devel-12.1-13.EL
> iiimf-libs-12.1-13.EL
> iiimf-gtk-12.1-13.EL
> iiimf-client-lib-11.4-43
> iiimf-x-12.1-13.EL
> iiimf-gnome-im-switcher-12.1-13.EL
> iiimf-le-unit-12.1-13.EL
> iiimf-client-lib-devel-11.4-43
> iiimf-server-12.1-13.EL
> iiimf-le-canna-12.1-13.EL
> iiimf-docs-12.1-13.EL
> iiimf-protocol-lib-devel-11.4-43
> 
> [root at localhost dave]# ps auxwww | grep httx
> root      4433  0.0  0.2  5272  664 pts/4    S+   18:38   0:00 grep httx
> 
> [root at localhost dave]# LANG=ja_JP.UTF-8 XMODIFIERS=@im=htt kedit
> QInputContext: no input method context available
> QInputContext: no input method context available
> 
> When I went to Google to look up this error, that's when I eventually 
> came across httx, but that's where I was stonewalled.
> 
> I hope someone can help me get this last piece of the puzzle in place.
> 
Do this to get httx on your machine:

yum install iiimf-docs iiimf-x

Here is the help it installs:

/usr/share/doc/IIIM/index.html

and

/usr/share/doc/IIIM/cmds/httx.html

I don't know any more about it than that ... I have never used iiimf.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.centos.org/pipermail/centos/attachments/20050807/4b017427/attachment-0002.sig>

Dave Gutteridge wrote:
>
> Japanese input - the final frontier. This is the last obstacle before 
> I can work completely within Centos and be free of Windows.
> But it's still not working.
>
> <SNIP>
> And here are the results of some of the commands they suggest to check 
> if iiimf is running in KDE:
> <SNIP>
> [root at localhost dave]# LANG=ja_JP.UTF-8 XMODIFIERS=@im=htt kedit
> QInputContext: no input method context available
> QInputContext: no input method context available
>
> When I went to Google to look up this error, that's when I eventually 
> came across httx, but that's where I was stonewalled.
>
> I hope someone can help me get this last piece of the puzzle in place.
I don't know if this will help, but I've got the iiim service running on
my CentOS 4 laptop at home.  I type the necessary shell variables 
followed by the command I want and it works quite well for Gnome/GTK 
applications.

I've successfully typed kana into GVIM and gedit without issue.  
CTRL-SPACE is used to turn on the non-Latin language set (a little Kanji 
character displays underneath the window to indicate the change in 
mode).  CTRL-SHIFT-SPACE is used to switch between Japanese, Korean, 
Chinese, and other language sets.  All of this appears to work just fine. 

I don't know how to get it to use Kanji though.  All I appear to get is 
hiragana.  I don't know very much Japanese and really can't read it 
without a kana chart and a dictionary.  My sister has had several years 
of Japanese in school and was nice enough to verify that, yes, it was 
displaying kana.  Unfortunately, when I typed in "neko" it displayed
the
hiragana and not the Kanji we were expecting.

Also, unfotunately for you, what doesn't work is KDE/QT apps.  I'm not 
sure yet as to why.  I run KDE for my desktop, but my of my apps are 
Gnome/GTK (go figure!).

I guess my reason for posting is to indicate to you that, yes, this does 
work for someone else, and yes, they are having the same problem with 
KDE apps.

--Shawn