From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Fedora/1.7.6-1.3.2 Description of problem: Kxkb doesn't support Korean keyboards. It's effectively impossible to input Korean under KDE. I've configured Kxkb to support Greek, French, and Korean. Switching to Greek and French keayboard mappings works: I'm able to input Greek and French. However switching to Korean doesn't work: the Kxkb tray icon displays a redd "err" message instead of "ko" as expected. Version-Release number of selected component (if applicable): kdebase-3.3.1-4.3.FC3 How reproducible: Always Steps to Reproduce: 1. Have Kxkb activated and running. 2. Configure it to support Korean and another language. 3. Switch to Korean by clicking on the tray icon. 4. The tray icon displays "err" and the previous keyboard mapping is used instead. Actual Results: The tray icon displays "err" and one can't input Korean. Expected Results: The tray icon displays "ko" and I can input Korean. Additional info: See also bug #112024. I had requested a Korean keyboard mapping. The fix was apprently to introduce a Korean keyboard mapping. I guess the current error is a consequence of that fix. FYI, here is my context: I understand there's more than keyboard mappings to Korean, and that I'd need some input method to be able to input Korean. My final goal is indeed to be able to input Korean under KDE. This does not seem to be possible - under a non-Korean locale at least. I wonder what is the reason for that? Is KDE totally broken with respect to i18n? Doesn't Fedora install KDE properly? Does it miss patches (I think KDE+i18n work much better on Mandrakelinux for example)?
Created attachment 113195 [details] error message in Kxkb tray icon
Created attachment 113196 [details] configuration panel of Kxkb Greek, French and Korean mappings are selected. The current locale is fr_FR.UTF-8.
I just upgraded to kde 3.5.1 on fc4-with-all-updates, and my Swiss-German layout isn´t available anymore.
i will push new kdebase into FC4 update this week, it should fix this problem. Thanks for your report