Re: How to localize keyEquivalent="q"?

[Paul Chany]

Robert Slover <rjslover@me.com> writes:

> It is worthwhile to read the Wikipedia article related to this
> subject.  http://en.wikipedia.org/wiki/Keyboard_shortcut .  Note that
> one of the two images used to illustrate the concept is a screenshot
> of WorldWideWeb.app running on NeXTStep :-D .  Note that they plainly
> state that "shortcuts" are not localized, but "mnemonics" are. 

I read it.

> Honestly, I still prefer mnemonics/accelerators to
>  key-equivalents/shortcuts.  The most productive menuing systems I
>  ever used were the Lotus-style menus in the old Borland products.
>  Just hit [F10] (menu), and start typing accelerators.  Effectively,
>  *everything* was quickly navigable from the keyboard, whether a
>  shortcut was defined or not.  Even if an accelerator was missing for
>  a menu entry, you could get there quickly with the arrow keys.  It is
>  amazing how fast those sequences became muscle memory, and allowing
>  sequences of characters means a much greater "namespace" for keyboard
>  menu access inside an application.  Contrast that to even the best
>  thought-out Mac application, where 4 or 5-key "chords" are often
>  necessary to get adequate shortcut coverage in any decently-sized
>  applicati on.

Mnemonics/accelerators are good indeed. They are localizable. :)
We haven't these in GNUstep applications, right?

-- 
Regards,
Paul Chany
You can freely correct my English.
http://csanyi-pal.info