- From: <bugzilla@jessica.w3.org>
- Date: Mon, 30 Mar 2015 00:52:06 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22524 --- Comment #4 from Abel Braaksma <abel.braaksma@xs4all.nl> --- Tim Mills wrote: > expected result starts with 0 (0), not a circled zero (①). Michael Kay wrote: > For example, the format token ① (circled digit one, ①) has a range > imposed by the Unicode character repertoire — 1 to 20 in Unicode versions > prior to 4.0, increased in subsequent versions. However, CIRCLED DIGIT ONE is U+2460, ZERO is U+24EA. They are not consecutive. Both have been around since Unicode 1.1. Are we suggesting here that the outcome from a processor should (optionally?) be: <out> 0 ① ② ③ ④ ⑤ ⑥ ⑦ ⑧ ⑨ ⑩ ⑪ ⑫ ⑬ ⑭ ⑮ ⑯ ⑰ ⑱ ⑲ ⑳ 21 22 23 24 25</out> Or: <out> ⓪ ① ② ③ ④ ⑤ ⑥ ⑦ ⑧ ⑨ ⑩ ⑪ ⑫ ⑬ ⑭ ⑮ ⑯ ⑰ ⑱ ⑲ ⑳ 21 22 23 24 25</out> Or even: <out> ⓪ ① ② ③ ④ ⑤ ⑥ ⑦ ⑧ ⑨ ⑩ ⑪ ⑫ ⑬ ⑭ ⑮ ⑯ ⑰ ⑱ ⑲ ⑳ ㉑ ㉒ ㉓ ㉔ ㉕</out> Numbers up to 50 have been supported since Unicode 3.3. These ranges are not consecutive: 0: 24EA (since 1.1, 1993) 1-20: 2460 - 2473 (since 1.1, 1993) 21-35: 3251 - 325F (since 3.2, 2002) 36-50: 32B1 - 32BF (since 3.2, 2002) So for these Unicode ranges in particular, it is incorrect that only 1 to 20 existed in Unicode prior to 4.0. All these circled digits where added earlier. This means that the sentence in the XSLT 3.0 spec is possibly incomplete: "For example, the formatting token ① (circled digit one) has a range of 1 to 20 imposed by the Unicode character repertoire." I am not sure how to move forward. Since these ranges fall under implementation-defined behavior (and add to that the supported Unicode version is implementation-defined as well), I don't think there's anything we can force here, so I propose that the result of the test should iterate these alternatives. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 30 March 2015 00:52:09 UTC