[i18n-activity] Code point representation

r12a has just created a new issue for 
https://github.com/w3c/i18n-activity:

== Code point representation ==
https://w3c.github.io/uievents-key/#style-conventions
1.1. Stylistic Conventions

>   Unicode character encodings are shown as: \u003d.

https://w3c.github.io/uievents-key/#key-value-tables
2. Keyboard Event key Value Tables, 2nd Note

> There are special internationalization considerations for ECMAScript
 escaped characters. CharMod conformance [CharMod] expects the use of 
code points rather than surrogate pairs in escapes. ECMAScript escaped
 characters use surrogate pairs for characters outside the Basic 
Multilingual Plane (\uD84E\uDDC2 for "𣧂", a Chinese character meaning 
"untidy"), rather than C-style fixed-length characters (\U000239c2 for
 "𣧂") or delimited escapes such as Numeric Character References 
("𣧂"). Characters escaped in this manner:
> 
> -     are based on UTF-16 encoding, in that it uses surrogate pairs 
for values outside the Basic Multilingual Plane
> -     are expressed using surrogate pairs, which makes it difficult 
for a human to look up the value, and might require unnecessary 
overhead for machine processing — this can also cause problems with 
software written in the incorrect belief that Unicode is a 16-bit 
character set
> -     are problematic for characters on supplementary planes (emoji,
 or Chinese characters on plane 2), some of which are expected to be 
input using a keyboard
> -     are not be suitable for Java or C, which use different 
escaping mechanisms (could be solved with a normalizing method)
> 

These are good points. (Another point would be that this annotation 
form ties the document to a specific implementation approach that will
 become redundant over time.  ES6 already supports a codepoint based 
escape format: \u{12345} )

Given the above points, and the fact that, as far as i can tell, in 
both this spec and the code spec, this convention is only used to 
identify Unicode code points, i don't understand why javascript 
escapes are being used to refer to code points – the normal approach 
would be to use U+003D.


Please view or discuss this issue at 
https://github.com/w3c/i18n-activity/issues/240 using your GitHub 
account

Received on Wednesday, 26 October 2016 18:40:02 UTC