W3C home > Mailing lists > Public > www-international@w3.org > October to December 2016

[uievents] Issue: Editorial: Capital letter equivalents for bicameral scripts marked as i18n-comment

From: r12a via GitHub <sysbot+gh@w3.org>
Date: Fri, 16 Dec 2016 14:16:04 +0000
To: www-international@w3.org
Message-ID: <issues.labeled-196068698-None-sysbot+gh@w3.org>
r12a has just labeled an issue for https://github.com/w3c/uievents as 
"i18n-comment":

== Editorial: Capital letter equivalents for bicameral scripts ==
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.

See https://github.com/w3c/uievents/issues/123
Received on Friday, 16 December 2016 14:16:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:11 UTC