Skip to content
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

Editorial: Capital letter equivalents for bicameral scripts #123

Closed
r12a opened this issue Dec 16, 2016 · 1 comment
Closed

Editorial: Capital letter equivalents for bicameral scripts #123

r12a opened this issue Dec 16, 2016 · 1 comment
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.

Comments

@r12a
Copy link

r12a commented Dec 16, 2016

5.1.1. Key Legends
https://w3c.github.io/uievents/#key-legends

For historical reasons, the character keys are typically marked with the capital-letter equivalents of the character value they produce, e.g., the G key (the key marked with the glyph "G"), will produce the character value "g" when pressed without an active modifier key (e.g., Shift) or modifier state (e.g., CapsLock).

Editorial: To be more accurate it may be better to say:

For historical reasons, on keyboards for bicameral scripts, the character keys are typically marked with the capital-letter equivalents...

I don't actually know whether this is true for all such scripts. May be worth a quick check. That would include keyboards for languages using Latin, Greek, Cyrillic, Armenian, Cherokee, Adlam.

(Less common bicameral scripts include Coptic, Warang Citi, Old Hungarian, Osage, Glagolitic and Deseret.

@r12a r12a added the i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. label Dec 16, 2016
@asmusf
Copy link

asmusf commented Dec 16, 2016

Then we have scripts like Cherokee, Georgian and also Hiragana/Katakana where the keys may be marked with one version of a series of parallel scripts (Cherokee is intended to be bicameral, but isn't supported the same way as other scripts in Unicode because of the late addition of the other case).

Perhaps better to simply say: "Sometimes the image on the key cap is not what you get when pressing a key in the unshifted state" and give a single! example rather than trying to make a general statement that's bound to run into some edge case.

triple-underscore added a commit to triple-underscore/triple-underscore.github.io that referenced this issue Jan 27, 2017
Commits on Jan 26, 2017

Fix
	w3c/uievents#110
Mark up IDL attributes properly
w3c/uievents@e7dc630
f780fba

Commits on Jan 25, 2017

Fix
	w3c/uievents#124
Remove MAY in non-normative section
w3c/uievents@19f060d
fa9cac1

Fix
	w3c/uievents#123
Remove paragraph on key cap capitals.
w3c/uievents@820eecd
2f3e2bb

Fix
	w3c/uievents#132
initCompositionEvent
w3c/uievents@d2227ad
8edafc6

Fix
	w3c/uievents#118
Typos
w3c/uievents@ac79bb5
ba3710f

Fix:
	w3c/uievents#117
	w3c/uievents#119
	w3c/uievents#121
Move 'key' algorithm into uievents-key
w3c/uievents@1791777
eaf055a

Remove "Key Values and Unicode" section
w3c/uievents@8c621f6
1b92d42

Minor typo/formatting fixes
w3c/uievents@709fd2b
21a36ad
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.
Projects
None yet
Development

No branches or pull requests

2 participants