GNOME Bugzilla – Bug 622197
GUI UI shortcut key choice (avoid: CTRL-SPACE, SHIFT/CTRL/ALT-Arrow used by CJK)
Last modified: 2019-02-27 15:16:25 UTC
This tool needs to accept keyboard input not just ASCII or deadkeys but Chinese/Japanese/Korean/Vetnamese/Thai/Arabic/... They usually use Input Method (IM) which translate simple keyboard input into selected codes with complicated huristics. Most of these IM UI on X/Linux platform uses following keys: CTRL-SPACE or SHIFT-SPACE: IM On/ IM Off (Via IM or Direct) ARROW, CTRL-ARROW or SHIFT-ARROW: IM input range selection and moving conversion scope So these keys must not be used as SHORTCUT! Popular Input methods which interfare with this are: * IBus (New GNOME) * SCIM (Old GNOME) * uim All these use CTRL-SPACE as normal on/off switch key. Gtranslator's choice of using these keys for its internal UI is very bad choice. I think the best thing is make these shortcut key choice configurable. If you really need some arrows, please stay within ALT-ARROWS. PGUP/PGDN, ALT-PGUP/PGDN. Also, F6-F10 are frequently used as special conversion instruction. May I suggest something like: COPY ORIGINAL MESSAGE: CTRL-B or CTRL-N Next/Prev fuzzy/untranslated (most used) PGUP/PGDN Next/Prev fuzzy ALT-CTRL PGUP/PGDN Next/Prev untranslated ALT-SHIFT PGUP/PGDN Next/Prev ALT- PGUP/PGDN First/Last CTRL-SHIFT PGUP/PGDN This seems reasonable choice .... http://bugs.debian.org/586116 Osamu
We are mass-closing old gtranslator issues as the latest versions of gtranslator (3.30 or later) should fix most of the reported problems and as there is unfortunately no capacity to retest all of them separately. https://mail.gnome.org/archives/desktop-devel-list/2019-February/msg00059.html If the issue described in this report still happens in gtranslator version 3.30 or later, please file a new ticket under https://gitlab.gnome.org/GNOME/gtranslator/issues/ - thanks for your understanding! We are sorry that your report was not handled / fixed after you reported it - many free and open source software projects receive more bug reports and feature requests than they have developers who have free time to work on them. If you would like to get involved and contribute on gtranslator code, please check https://wiki.gnome.org/Git/Developers