-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hotkey shouldn't be capitalized #2168
Comments
fwiw, http://blog.i18n.ro/keyboard-shortcuts-and-mnemonics-or-accelerators-are-not-the-same-thing/ |
What about languages without capitalized letters (Arabic, Japan, Chiese, Korean etc)? |
Using the terminology of that website, this bugreport is about mnemonics. |
Created 2168_capitalized_hotkeys branch. Parent branch is master. |
|
|
|
|
Important
This issue was migrated from Trac:
egmont
(@egmontkob)In some contexts, e.g. in the F9 menu, hotkeys are highlighted using a different color, no matter if it's an uppercase or lowercase letter. Capitalization of the letters is independent of the hotkey: the first letter, and acronyms are capitalized.
In some other contexts, e.g. in the file copy dialog, hotkeys are the ones that are capitalized, instead of the first letter. For example, there's a "diVe into subdir" instead of "Dive into subdir", since V is the hotkey.
These two looks are inconsistent. I think we should decide on one of the schemes and consistently go with that one.
I personally recommend going with the current scheme of the F9 menu. Hotkeys are already highlighted by the color; I don't see any point in using yet another attribute (uppercase) for emphasizing them even more. Capitalizing a letter in the middle of a word looks ugly. The scheme cannot really be used if there's an acronym, or at least it would really look weird. Moreover, some translations might already be using that scheme (I only checked Hungarian and that one is consistent with itself: even in the file copy dialog it always capitalizes the first word, not the hotkey.)
The text was updated successfully, but these errors were encountered: