Issue 87393 - keyboard shortcuts aren't consistent when using localizations
Summary: keyboard shortcuts aren't consistent when using localizations
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 2.4 RC5
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: thorsten.martens
QA Contact: issues@framework
Keywords: oooqa
Depends on:
Blocks: 81913
  Show dependency tree
Reported: 2008-03-24 23:27 UTC by ccheney
Modified: 2010-05-17 21:38 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description ccheney 2008-03-24 23:27:27 UTC
From the Ubuntu bug report:

gnome uses a pretty standard keyboard shorcut scheme, for example to save
something in gedit/dia/gimp... you must press ctrl+s. This binding is always the
same in all of gnome's localizations (at least in the spanish & english one).
Other apps like openoffice change the scheme depending on the language (in
spanish to save the file it's ctrl+g). I think it's very inconsistent & is an
usability problem. It makes the user remember to use different keyboard
shortcuts with the same meaning on different context. All apps should use the
same keyboard shortcuts in the same localization (or better, all apps should use
the same keyboard shortcuts in all localizations)

NOTE: I know this happens in openoffice. In Firefox it doesn't happen, but I
don't know if it may happen in other apps, so that's why I haven't assigned the
bug to the ooo2 package.


This also leads to other problems like bug 87113, where OOo tries to use the
same keyboard shortcut as Gnome.
Comment 1 lohmaier 2010-05-17 21:37:23 UTC
OOo is a cross-platform suite and has many, many features, usually much more 
than your general desktop utility.

There will never be a way to have mnemonics that don't conflict with any other 

If you got a problem with a specific localization, it's best to discuss it with 
the corresponding native-lang project and have the correpsonding project lead 
request the change.

This issue is way to generic to be handled in a useful way.
Comment 2 lohmaier 2010-05-17 21:38:16 UTC
closing issue.