To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=77968


User cloph changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|RESOLVED                  |CLOSED
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Fri May 22 14:45:27 +0000 
2009 -------
invalid because nothing that can be fixed - OOo cannot grab shortcuts that are
interpreted by the system before being passed to OOo.

And different behaviour while writing in writer/calc: Very likely caused by a
distribution-specific patch to OOo that tries to be clever to not use GTK-Input
method because of the unfortunate keyboard-combos that GTK did use for that at
the beginning) but of course failed because not disabled for all modes.

closing. GTK did change the unicode-input shortcut to a more sensible shortcut
(ctrl+shift+u) anyway (clashes with german shortcut for underline, but same
reasoning for invalid applies). If you aim to use sensible keys for shortcuts
like in this case <ctrl>+<shift>+f/k/u (fett/bold, kursiv/italics,
unterstrichen/underlined, with <ctrl>+<shift> because <ctrl>+f now defaults to
Find because of interoperability), then you have take into account that some
combinations will clash.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to