Japanese input with scim-anthy
Hi all I can't seem to get Japanese input working with scim-anthy. I have scim 1.4.9 installed and the daemon running. I have the scim-anthy 1.3.1 package installed as well. I can open and modify the scim-settings, but I can't get the anthy dialog to appear. Apparently, ctrl-space should bring up the dialog, but nothing happens. I tried following the instructions on this page under "Open a program with japanese input enabled - via command line", but still no dialog.
After starting the daemon, I tried: Code:
XMODIFIERS='@im=SCIM' LC_CTYPE=en_US.UTF-8 gvim |
What version of Slackware are you using?
Also, issue "dmesg | grep scim" and post anything that it outputs. Follow the instructions from CHANGES_AND_HINTS.TXT that came with Slackware: Quote:
Right-click on it and choose SCIM Setup. Then under IMEngine click on Global Setup and then in the window on the right remove all the input methods that you don't need. For me it's easiest just to select Disable All and then go and manually check the input methods I need. After that you will have to restart the SCIM service. Should be as easy as clicking Exit on the SCIM icon, but in Slackware that doesn't work. To be sure it's restarted properly you should close the X server, KDE or whatever one you use, and then restart it. After that you should be able to open an app and then press Ctrl + Space to start SCIM input. If you follow these instructions and have problems, please post back. If you are using Slackware Linux, instructions for another distro might not work. |
Try like this:
Code:
export XMODIFIERS="@im=SCIM" |
Quote:
Quote:
Code:
[matt@hopper] $ dmesg | grep scim Quote:
I'm not sure that I'm doing this right. Should I be able to open, say, Firefox or OpenOffice, hit ctrl-space, and then some dialog box should pop up? When I do this, nothing happens :( |
Also, I don't know if this is relevant or not, but when I start scim without specifying a front end, it starts fine:
Code:
[Fri Nov 12, 01:22:59] [~] Code:
[Fri Nov 12, 01:21:56] [~] |
Quote:
Note that I don't want everything to be in Japanese, I just want to be able to enter Japanese text. I am learning the language and need to be able to search for things and communicate with people, but don't want my whole environment to be changed. |
Did you try ibus from sbopkg?
|
Hi mattca,how did you get scim-anthy 1.3.1 package?
Even in slackware-current, scim-anthy version is only 1.2.4,I was wondering whether there is a confict.Also, did you got anthy package installed?' Below is what I did, it do work even in my chinese envionment. Code:
slackpkg install anthy Code:
anthy-9100h-i486-1.txz Code:
scim -d Code:
scim -f anthy -d |
Quote:
http://sourceforge.jp/projects/scim-imengine/ Quote:
Code:
2. Requirements I might not have done it in the right order though, if a certain order is necessary. Maybe I'll remove everything and reinstall. Quote:
I have Code:
anthy-9026.tar.gz Quote:
Also, I'm not sure that I'm using it right. Just so that I understand, once it is set up properly, and the scim daemon is running the background, I should be able to open an application - say, Firefox, Open Office, gvim - hit Ctrl-Space, and then a dialog box should pop up allowing me to input Japanese characters. Is that correct? Thanks. |
Quote:
|
SCIM is no longer being maintained. The developers work for RedHat,
and they have been pulled off of SCIM. They are now maintaining iBus, so it would be good to build your own iBus packages for Slackware. SCIM is also not properly patched in Slackware, so that gives you another incentive. iBus is working fine for me. |
Quote:
Then restart scim -d ...... Maybe all you problem is due to this...... |
Quote:
|
Thanks for the help everyone, but I ended up getting JWPce working through WINE. I don't know what the issue was with scim, and ibus requires GConf and I avoid anything Gnome-related like the plague, so that wasn't a good option for me. JWPce is good enough for my purposes.. I can copy and paste it wherever I need it.
Also, I know where to get Slackware packages.. I just prefer to install from source. Actually, my wine install was a good example of why. The slackbuild wouldn't work on my system - it complained about an unimplemented function. I installed from source, and it worked fine on the first go. I only use packages if source is not an option, which doesn't happen very often. I think OpenOffice is the only thing I have consistently used the slackbuild for. |
mattca,
If you are comfortable building from source, that is splendid. However, in order to better manage packages on your system, it is my suggestion to build and install them with SlackBuild scripts. If you're not familiar with that, a good starting place would be the the tool called Alien's SlackBuild Toolkit that Eric Hameleers wrote just specifically for this purpose. Glad you got Japanese input working on your computer. |
All times are GMT -5. The time now is 10:46 AM. |