Strategies for localising keyboard shortcuts

Question

I'm currently involved in a heavily localised WPF application and we've had a bug raised about keyboard shortcuts on menus in non-English languages. The bug referred to modifer key names (Shift, Ctrl, etc.) not being translated, which is easy enough to fix.

However, this got me thinking about the shortcut keys themselves, which are often based on the first letter of the command, except where this isn't feasible due to clashes or convention. When the command names are localised this link between the commands and their respective shortcuts will usually be lost:

• Is this worth worrying about?
• How do existing major applications cope with this problem?
• Are there any other issues to consider in this case?

Although this question was inspired by a WPF app, I'm more interested in the general case.

Answer 1

You should stay away from symbol-keys (such as * and <), since they tend to move around on international keyboards. See Wikipedia: Keyboard layout

If you plan on switching the letters around depending on localization, you should enable the user to choose if he/she wants the English variants instead. It is frustrating if I have to learn two sets of shortcuts depending on the language. (Same goes for cross-platform applications.)

Best would be fully customizable keyboard shortcuts, but that could be more for power-users. See Media Player Classic for an example.