Help with Japanese language input using ibus, ibut-anthy
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Help with Japanese language input using ibus, ibut-anthy
Trying to install ibus on Slackware 14.2, with out much success, there three packages that are need, pyxdg, ibus-anthy, and ibus-qt, but they are not available on SlackBuilds, page 404 shows up if a download is done!
However they are available from other sites!
IBUS was originally commissioned by Red Hat Linux, and it works well on Red Had and its derivatives! Installing it on Slackware, the first message that comes up is:
IBus has been started! If you can not use IBus, please add below lines in $HOME/.bashrc, and relogin your desktop.
export GTK_IM_MODULE=ibus
export XMODIFIERS=@im=ibus
export QT_IM_MODULE=ibus
creating .basherc or .bash_profile and doing that still get that message, and error message, adding this line export LC_CTYPE=en_US.UTF-8
export GTK_IM_MODULE=ibus
export XMODIFIERS=@im=ibus
export QT_IM_MODULE=ibus
export LC_CTYPE=en_US.UTF-8
eliminates the error message, but still ask to create .bashrc and insert the lines etc.
The main problem is that Slackware unlike Red Hat, does not have .bashrc etc, it is not build in its system. here is a case where this problem has been avoid and circumvented , but still does not yield a satisfactory result:
these are placed in .bashrc, and same result as usual comes up!
I managed to install it but after first use, it crashes, hovering mouse on the icon, which is a keyboard icon , shows main.py and clicking on it give a message: no input window, can any one help, especailly a Japanese speaker?
You can search and find the packages on other sites (like http://pkgs.fedoraproject.org).
Download them and put them into /var/cache/sbopkg and use sbopkg to build them.
@Qury: I don't think that's easy and it is not recommended to install from other distributions sources, generally speaking.
@kujirasan. I have pointed a Japanese Slackware user to this thread, hopefully he will be able to help you.
PS Additionally you can try to get help from the Plamo (Japanese Slackware derivative) project. They seem to use ibus but I am unable to understand the message in the attached pic, sorry.
PPS The person I wrote to is not registered on linuxquestions but he suggests that you use SCIM instead.
Like I said, this is geared for -current, but it should work on 14.2 as well, maybe with some minor adjustments. Some dependencies are listed in the "NOTES" file, but if something
is still unclear you can ask me and I'll try to clarify.
There are both ibus and fcitx in there, you can install and evaluate both (they co-exist just fine), but from personal experience, I prefer fcitx over ibus (I use it for Japanese input too).
As input method, anthy is in there too, however, I'd suggest you try kkc, which is newer.
Setup with those packages should be a bit simpler than with the versions on SlackBuilds.org. ibus and fcitx start automatically on login (for xdg compliant desktops like xfce or kde).
You only have to configure which one you want by placing these lines in .bashrc:
Above shows the config for fcitx. If you want to use ibus, just replace 'fcitx' with 'ibus'. If you don't have a .bashrc, you can just create a new one. No further config should be necessary (particularly, no extra config files in xinput.d or some such. Probably good though if you remove those again).
Thanks for the replies, very much appreciated, unfortunately not much luck! Here are the error messages , after
adding to .bashrc
the following lines:
export XMODIFIERS="@im=ibus"
export XIM=ibus
export XIM_PROGRAM=ibus
export GTK_IM_MODULE=ibus
export QT_IM_MODULE=ibus
ibus-setup
(main.py:1645): IBUS-WARNING **: Connect to unix:abstract=/tmp/dbus-2wzFw4W8ep,guid=781019644f07cf1ac0fa6bde590163ea failed: Failed to connect to socket /tmp/dbus-2wzFw4W8ep: Connecti
# ibus-setup
(main.py:1648): IBUS-WARNING **: Connect to unix:abstract=/tmp/dbus-2wzFw4W8ep,guid=781019644f07cf1ac0fa6bde590163ea failed: Failed to connect to socket /tmp/dbus-2wzFw4W8ep: Connection refused.
/usr/libexec/ibus-engine-m17n: error while loading shared libraries: libibus-1.0.so.5: cannot open shared object file: No such file or directory
Sorry, I don't know which steps you exactly took to get here. Did you create packages from the SlackBuilds I linked? Or do you still have the packages created from the SlackBuilds on SBo installed?
The error indicates that you have ibus-m17n installed that is still linked to an older version of ibus, so you'd need to recompile or remove that one.
I have clean install of 14.2 , on Virtualbox, made a clone, of 14.2, the only thing is on it is pyxdg, and python 2.7 which is default, would you recommend installing python3.6.1, or is not necessary?
the following packages I have downloaded:
Not sure why they'd end up with .txt extensions, but I don't think the extension matters much. Just make them executable and run them. Python 2.7 is fine, no need for Python 3.
However, do make sure you have *all* files in the respective folders and also make sure to have downloaded the dependencies for the packages you listed above, otherwise the builds will fail.
I have clean install of 14.2 , on Virtualbox, made a clone, of 14.2, the only thing is on it is pyxdg, and python 2.7 which is default, would you recommend installing python3.6.1, or is not necessary?
the following packages I have downloaded:
How would you install these? converting the txt to run?
Hi,
I would do the following:
Download sbopkg
sync the slackbuilds
build the build queues using sqg -a
if the source files are not available from the sbopkg.org defined location, then track them down from somewhere else, check the mdsum to ensure they are not some other packages otherwise the build will fail.
drop the source files into /var/sbopkg/cache
assuming the queue files are generated, i would use sbopkg -i packagename to build whatever you need, and accept build queue whenever sbopkg prompts you for it
Then follow the slackware specific instructions for the packages to configure them if they require any additional configuration. (/etc/profiles.d/, etc..)
if the source files are not available from the sbopkg.org defined location, then track them down from somewhere else, check the mdsum to ensure they are not some other packages otherwise the build will fail.
drop the source files into /var/sbopkg/cache
assuming the queue files are generated, i would use sbopkg -i packagename to build whatever you need, and accept build queue whenever sbopkg prompts you for it
Then follow the slackware specific instructions for the packages to configure them if they require any additional configuration. (/etc/profiles.d/, etc..)
For SlackBuilds on SBo, this advice is sound. However, sbopkg won't work with the SlackBuilds I linked, so not sure what this adds...
ppr:kut, I will try to download all the dependency files etc, just installing them is difficult!
Qury: usning sqg -a is not a good idea, it takes long time, and if your internet is not reliable can be a probelm, but it can cause disaster and wreak havoc, give you an example, I did a sqp -a, and installed qupzilla browser, it installed 200 more packages actually anything that was qt, and then it knocked of KDE decoration, and max min delete buttons disappeared, so better do a sqp -p filename and one at a time !
Laserbeak: One step in the right direction would be to change LC_CTYPE=en_US.UTF-8 to LC_CTYPE=ja_JP.UTF-8 on that .bashrc file you created.
That was done, it does not work, just reduces the error output when you type, #ibus-setup!
Thanking you very much for your input and time, very much appreciated, such a wonderful people!
Qury: usning sqg -a is not a good idea, it takes long time, and if your internet is not reliable can be a probelm, but it can cause disaster and wreak havoc, give you an example, I did a sqp -a, and installed qupzilla browser, it installed 200 more packages actually anything that was qt, and then it knocked of KDE decoration, and max min delete buttons disappeared, so better do a sqp -p filename and one at a time !
I see how that can be a problem as it pulls in qt5.
My personal preference with sbopkg/slackbuilds is to install qt5 and ffmpeg from alienbob but use sbopkg for anything else.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.