I cant use ibus to input Korean and Japanese

[ScegfOd]

no matter what I've tried I can't seem to get ibus to type either Korean or Japanese... decided to try french since that was in some example i looked up somewhere... it changed the key order ! but i still cant get it to type what i need
I've tried adding the export stuff to .bashrc and .bash_profile (is that different from .xprofile?) and i've tried adding all the fonts i could find... I forget what else I tried

also... I can get ibus to start by manually finding the ibus-setup and starting that, which will give me a popup to run the daemon, but I cant get ibus to start automatically

also, I'm using the LXDE Mageia 3 64bit DVD install on a laptop...is that important?

[doktor5000]

Did you check https://wiki.mageia.org/en/Mageia_3_Errata#ibus ?

[ScegfOd]

thanks for the reply, I have looked at that page at least a couple times.
my software manager says i have "ibus-ui-gtk3" installed.
also I've managed to start the ibus daemon, but never automatically on startup/login
Also, I've managed to add the french language which seems to have only changed the order of my keys when I used it (for 1 example the a and q keys switched).

I also added Korean (Korean) and Japanese (Anthy), but they don't seem to do anything different from English (English (US))

infact, I think ill try another thing besides french... howbout Dvorak

English (English (US))
abcdefghijklmnopqrstuvwxyz

vs

English (English (Dvorak))
axje.uidchtnmbrl'poygk,qf;

so it can do some things...but my ibus doesn't like Korean or Japanese for some reason... I think I have the proper fonts and I can read Korean and Japanese in Mozilla Firefox ...

edit:
i just realized that switching to dvorak didn't actually give me the dvorak keyboard...
',.pyf =/= dvorak
could there be something wrong with my laptop's keyboard settings?

[kateto]

I can confirm the same issue. Impossible to type Korean here. I'm using LXDE in Mageia 3 on a 32 intel processor with a Catalan locale, if that matters, and I installed from the full DVD, not the Live one. Followed the errata, clicked the greyed menu items, selected and set up several Korean input methods, but none of them seem to work: they only type English. I've tried Opera, Skype, LXTerminal, Firefox, Leafpad, and Libreoffice, same problem everywhere.

Is this a usability problem? ibus-setup doesn't show any way to be properly configured, besides the keys to switch to next input method. I remember it to be much more configurable in Mageia 2. From that version I still keep a bunch of XML configuration files in ~/.gconf/desktop/ibus that don't seem to get used anymore, and I don't know where it's putting its configuration files now. What on earth is the key combination to switch from Roman letters to Hangul??

For more info:

Code: Select all

[ruben@localhost ~]$ rpm -qa | grep ibus
libuser1-0.59-1.mga3
libusb1.0_0-1.0.14-2.mga3
ibus-ui-gtk3-1.5.1-2.mga3
ibus-hangul-1.4.1-3.mga3
libibus1.0_5-1.5.1-2.mga3
libusb-compat0.1_4-0.1.4-3.mga3
ibus-m17n-1.3.4-3.mga3
libibus-gir1.0-1.5.1-2.mga3
ibus-table-1.4.99.20121112-2.mga3
scribus-1.4.2-1.mga3
libuser-0.59-1.mga3
ibus-1.5.1-2.mga3

[ruben@localhost ~]$ rpm -qa | grep hangul
ibus-hangul-1.4.1-3.mga3
libhangul1-0.1.0-2.mga3
libhangul-0.1.0-2.mga3

[ruben@localhost ~]$ rpm -qa | grep korean
fonts-ttf-korean-1.0.2-0.080608.4.mga3

Also, here's my .i18n file, created by draklocale:

Code: Select all

LANGUAGE=ca:es_ES:es
GTK_IM_MODULE=ibus
LC_ADDRESS=ca_AD.UTF-8
LC_COLLATE=ca_AD.UTF-8
QT_IM_MODULE=ibus
LC_NAME=ca_AD.UTF-8
LC_NUMERIC=ca_AD.UTF-8
LC_MEASUREMENT=ca_AD.UTF-8
LC_TIME=ca_AD.UTF-8
LANG=ca_AD.UTF-8
LC_IDENTIFICATION=ca_AD.UTF-8
LC_MESSAGES=ca_AD.UTF-8
LC_CTYPE=ca_AD.UTF-8
LC_TELEPHONE=ca_AD.UTF-8
LC_MONETARY=ca_AD.UTF-8
XIM_PROGRAM="ibus-daemon -d -x"
LC_PAPER=ca_AD.UTF-8
XMODIFIERS=@im=ibus


By the way, this file can't launch ibus at login anymore as it did on Mageia 2. I know I can add the relevant lines at .bashrc, but then, why drakelocale still offers the option of setting up an input method? It should be removed if it doesn't work. Should I file a bug report?