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

[uievents] Issue: Use U+ notation to refer to code points marked as i18n-comment

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

== Use U+ notation to refer to code points ==
Applies to uievents, uievents-key and uievents-code specs.

Given the reasons enumerated in 
https://github.com/w3c/i18n-activity/issues/240 that javascript 
escapes are not great for representing code point values, why you are 
using that notation (eg. \u003D) to identify code points rather than 
the standard notation (eg. U+003D)?

Using the U+ makes it easier to refer in the specs to a character such
 as 𣧂 or to emoji - ie. you would write U+239C2 rather than the 
completely unhelpful \uD84E\uDDC2.

We propose you change this notation throughout the three specs.

See https://github.com/w3c/uievents/issues/127
Received on Friday, 16 December 2016 14:23:32 UTC

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