Bug 889533
Summary: | No Default Shortcut Key to turn on/off input method | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tommy He <lovenemesis> |
Component: | control-center | Assignee: | Control Center Maintainer <control-center-maint> |
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 18 | CC: | aalam, control-center-maint, damage3025, i18n-bugs, kem, liangsuilong, mikeandmore, mkasik, pwu, rstrode, tiansworld |
Target Milestone: | --- | Keywords: | i18n |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-06-04 02:24:08 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tommy He
2012-12-21 16:00:08 UTC
I understand the main concern is default setting is somehow different for different language/region, but I think beside that, what type of application does user use is also related. The new keyboard architecture in GNOME restricted a lot of technical possibilities. Previously applications that conflict with the input method key just disable the input method, which will not create any input contexts. However in this new architecture, it is not aware of input contexts and this conflicting key will always be intercepted by GNOME. For example, if you set Control-<space> as next-language-source, you will *never* be able to use Emacs. If you set to Super-<space> you will *never* be able to use kupfer or Gnome-Do (if I remember the default binding correctly...). Anyway, the reason I bring this issue up is this problem is *very complicated* under the current input architecture of GNOME. (In reply to comment #1) > I understand the main concern is default setting is somehow different for > different language/region, but I think beside that, what type of application > does user use is also related. > > The new keyboard architecture in GNOME restricted a lot of technical > possibilities. Previously applications that conflict with the input method > key just disable the input method, which will not create any input contexts. > However in this new architecture, it is not aware of input contexts and this > conflicting key will always be intercepted by GNOME. > > For example, if you set Control-<space> as next-language-source, you will > *never* be able to use Emacs. If you set to Super-<space> you will *never* > be able to use kupfer or Gnome-Do (if I remember the default binding > correctly...). Anyway, the reason I bring this issue up is this problem is > *very complicated* under the current input architecture of GNOME. Thanks Mike to bring it up. If needed, please file a separate issue for this Feature Request. For this one, please focus to define a default on/off shortcut key for a given language. (In reply to comment #2) > (In reply to comment #1) > > I understand the main concern is default setting is somehow different for > > different language/region, but I think beside that, what type of application > > does user use is also related. > > > > The new keyboard architecture in GNOME restricted a lot of technical > > possibilities. Previously applications that conflict with the input method > > key just disable the input method, which will not create any input contexts. > > However in this new architecture, it is not aware of input contexts and this > > conflicting key will always be intercepted by GNOME. > > > > For example, if you set Control-<space> as next-language-source, you will > > *never* be able to use Emacs. If you set to Super-<space> you will *never* > > be able to use kupfer or Gnome-Do (if I remember the default binding > > correctly...). Anyway, the reason I bring this issue up is this problem is > > *very complicated* under the current input architecture of GNOME. > > Thanks Mike to bring it up. If needed, please file a separate issue for this > Feature Request. > > For this one, please focus to define a default on/off shortcut key for a > given language. with gnome-3.8 (in Fedora 19) defined shortcut key (Super+Space) https://live.gnome.org/GnomeOS/Design/Whiteboards/KeyboardShortcuts Verified in GNOME 3.8 in Fedora 19. The default key is SUPER + SPACE, which is the same as in Win8. |