Description of problem: Current version of system-config-keyboard doesn't have Korean keyboard option. The latest kernel supports Korean Keyboard now. edit in /etc/X11/Xmodmap keycode 109 = Hangul_Hanja keycode 113 = Hangul #xmodmap /etc/X11/Xmodmap or #setxbmap kr Version-Release number of selected component (if applicable): kernel-2.6.18-1.2798.fc6 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Please See bug 204158
system-config-keyboard just uses rhpl to provide keyboard model info. reassigning
other ways to set up Hangul keyboard in manually vi /etc/X11/xorg.conf Option "XkbLayout" "kr" or set up in gnome-keyboard-properties However, anaconda and system-config-keyboard doesn't support yet.
I checked system-config-keyboard. It will change console and Xorg keyboard's settings. But the console setting tools loadkeys doesn't support kr layout now. We should ask kbd to support it first.
Hi phuang Can it change only Xorg keyboard's settings by system-config-keyboard? Because, currently SCIM is major IM on RHEL5 and FC6, and SCIM launchs on x11. Doesn't really need to use Korean keyboard on the console.
Hi jko, I found some codes in rhpl listed below. Currently, s-c-k uses console layout as diction's key, so we can not make two settings use same console layout, the first record will be overwrite by others (with same console layout). So if we do not make a big change (modify data structures) in s-c-k and rhpl, we can not support kr. Or we must add a kr layout for console. :( # NOTE: to add a keyboard model to this dict, copy the comment # above all of them, and then the key should be the console layout # name. val is [N_('keyboard|Keyboard Name'), xlayout, kbmodel, # variant, options] self._modelDict = { ... 'us' : [N_('keyboard|Korean'), 'us', 'pc105', '', ''], ... ... 'us' : [N_('keyboard|U.S. English'), 'us', 'pc105', '', ''], }
Created attachment 145155 [details] Add Korean keys layout support Add Korean keys layout support. And it need kbd >= 1.12-21 (it added Korean support too).
I checked the new source code. The name of Korean X key layout should be 'kr'. + 'ko' : [N_('keyboard|Korean'), 'kr', 'pc105', '', ''], ~~~
Fixed in 0.199-1.
Hi phuang, Will Hangul Keyboard option be included in anaconda?
Hi jko, I checked the code. Anaconda invokes rhpl. So it should support Korean keyboard too. We could test it in a future beta release.
Thanks Phuang, Yes, It is. I will test it in the future best release.
system-config-keyboard has 'kr' included, but not option found in system config as mention in bug -- keycode 109 = Hangul_Hanja keycode 113 = Hangul -- anybody please update what need to check
User pnasrat's account has been closed
I believe this is fixed in F7 already.
Sorry may still need to address comment 13.
Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
requested by Jens Petersen (#27995)
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
I see this bug was reopened, but I see no additional comments indicating why. Closing out again for now. If it's not actually fixed, please say that instead of just reopening it. Thanks.