> 2. Have a normative definition near the beginning like this: "Within this specification, the ambiguous term <dfn>character</dfn> is used as a friendlier synonym for Unicode code point." This is what CSS Text does, except that there "character" means grapheme cluster rather than code point. I prefer this option. I think there should also be a note reminding the reader that a "code point" is a single entity with a value from U+0000 through U+10FFFF, i.e. surrogate pairs do not appear after conversion from the input encoding. (This needs clarification because the terms "code point" and "code unit" are confusingly similar, and because JavaScript uses code units in this context (iirc).) > 1. feels verbose, but 2. means two different definitions of the same term in two different spec, which definitely smells bad. The contexts are sufficiently distinct that I don't think 2. will be a source of confusion. zwReceived on Monday, 12 August 2013 13:52:38 UTC
This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:30 UTC