Description of problem: caps lock is on, can't switch hangul,anthy <-> english Version-Release number of selected component (if applicable): 1.4.7-8.fc9.i386 How reproducible: always Steps to Reproduce: 1. caps lock is on 2. press shift + space key or hangul key 3. Actual results: Expected results: Additional info: scim-hangul-0.3.2-1.fc9.i386 scim-anthy-1.2.4-4.fc9.i386
I added CapsLock checkbox in keyselection dialog. If you want to shift + space + capslock works, you should scim-setup to add shift + space + capslock hotkeys. Fixed in 1.4.7-14.
It might be better if CapsLock was ignored.
hmm, I don't understand commnet #1 . Caps Lock is ON -> can't switch Korean Input Method <-> English Input Method. This is bug. See Also: http://sourceforge.net/tracker/index.php?func=detail&aid=1593151&group_id=108454&atid=650539 http://sourceforge.net/tracker/index.php?func=detail&aid=1707688&group_id=108454&atid=650539
Created attachment 296856 [details] Screenshot for keyselection dialog You should check the CapsLock CheckBox to let Ctrl + Space work with CapsLock on. Please look the screenshot.
(In reply to comment #4) > Created an attachment (id=296856) [edit] > Screenshot for keyselection dialog > > You should check the CapsLock CheckBox to let Ctrl + Space work with CapsLock > on. Please look the screenshot. O.K. Thank. Then, this method is very hard and complicated for End Usr.
Did you add Hotkey with CapsLock mask? Please see attached screenshot in comment #4.
I tend to agree with Sangu that it would be better not to mask capslock but just ignore it if possible.
I modified default config to ignore capslock mask. You should remove your ~/.scim/config and update scim-1.4.7-20. Fixed in scim-1.4.7-20.
Created attachment 298847 [details] After relogin , default ~/.scim/config (made automatically) in scim-1.4.7-20. (In reply to comment #8) > I modified default config to ignore capslock mask. You should remove your > ~/.scim/config and update scim-1.4.7-20. Update scim-1.4.7-20, logout -> ctrl+alt+F1 -> $rm ~/.scim/config -> ctrl+alt+F7 -> login > Fixed in scim-1.4.7-20. Caps Lock key problem still happens. Not Fixed.
I tested it with scim im module. It does not have problem. But scim-birdge does not work. I will fix scim-bridge.
- Caplock On in scim im module(xim) When inputing hangul, "capslock on" is equal with shift key. <-- this is bug in hangul input.
I rechecked the code of scim and scim-bridge. For fixing this problem, I need add code in scim-birdge gtk im module and qt im module, to ignore capslock mask. It needs a lot of works. And maybe it will cause other problems. I just tested scim im module in scim-1.4.7-20 that ignore capslock key mask. I found many IMEngines have problems. It is because many IMEngines will test capslock and use the different key processing logice when capslock is on. But capslock mask is ignored in 1.4.7-20. So I think the best solution is like 1.4.7-14. Add capslock mask in hotkey selection UI. Hi Jens, What's your opinion?
Okay sounds like this needs more thought and testing. I suggest we defer it to F10.
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
Huang Peng, do you want to take another stab at this, or what is your view now?
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.