Apache OpenOffice (AOO) Bugzilla – Issue 50547
[GTK+ vclplug IIIMF input improvements] shortcuts not working in pre-edit mode
Last modified: 2013-07-30 02:16:39 UTC
REPRODUCTION: ============= 1. login to JDS3 with japanese language 2. bring up cws "pl04" 3. enable japanese IM and start typing "lalelu" 4. without committing the string try e.g. "Ctrl + O" or "Alt + E" or whatever => shortcuts apparently interpreted by the IM
We would have to check whether a key input event is a shortcut BEFORE asking the IM - i'll investigate whether we can achieve that without an incompatible change which would affect the target.
oops, reset target
I asked cd and currently we cannot know whether a key would trigger a shortcut without actually dispatching it. This cannot be changed compatible, which rules out 2.0.x IMHO. So setting the target to "later" Essentially the IME should not filter these events since it does not use them.
*** Issue 50626 has been marked as a duplicate of this issue. ***
Issue 57023 (via issue 50626) has been marked as a duplicate of this bug. I use OO2.0 in gnome on suse9.0 linux. But i used OO1.1, 1.4 and 1.5 before without this problem. I really don't understand. I also don't understand the comments the issue 57023: [AND I don't find issue 57023 nor 50626 nor this one in "My issues" - that's an issue for the issue tracker.] ------- Additional comments from es Mon Oct 31 07:25:21 -0800 2005 ------- As a workaround, when starting OOo from a terminal, set the environnment variable like this: setenv SAL_USE_VCLPLUGIN kde or export SAL_USE_VCLPLUGIN=kde You won't get the typical GTK look&Feel but you'll be able to use those shortcuts. ------- Additional comments from cloph Mon Oct 31 13:58:59 -0800 2005 ------- The real solution is of course not to abandon the GTK-VCL-plugin but to * either not use GTK-input method or * map the shortcuts to another combo. So "GTK_IM_MODULE=xim" will do the trick (use "regular" x-input-method instead of the gtk-input-method) without sacrifying the gtk-integration.
the underlined big F is a feature of gtk's input method; OOo never really sees that you press ctrl-alt-shift-f because the input method filters this event. The idea of gtk seems to be that you can enter unicode sequences that will be converted on the fly to the according character, e.g. entering "ctrl-alt-shift-f" "ctrl-alt-shift-a" "enter" will produce the unicode letter 0xfa (which happens to be an accented upper case U). The bottom line is that the gtk library which all Gnome applications and nowadays OOo is based on swallows these key presses and therefore OOo cannot react on them. You did not have the problem in OOo 1.1 because that version did not use gtk. The mentioned workaround (setting SAL_USE_VCLPLUGIN) will give you the old behaviour; the IMHO better workaround to only use another input method in gtk will switch off (among others) this unicode entering feature so OOo can see the "ctrl-alt-shift-f" again. I hope this makes things a little clearer
*** Issue 64052 has been marked as a duplicate of this issue. ***
I can confirm this issue for the german version, too. Hexadecimal digits in combination with control + shift are not translated into OOo2 shortcuts. The suggested workarounds are unsatisfactory for production use of this product, thus no OOo2 and Gnome in our department. Note of interest: OOo2 in Gnome on SUSE's 10.1 version DOES NOT show this behaviour. There everything works as expected. Regards
target
*** Issue 105416 has been marked as a duplicate of this issue. ***
Reset assignee on issues not touched by assignee in more than 2000 days.