- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 8 Jul 2010 09:34:26 -0700
- To: Yuzo Fujishima <yuzo@google.com>
- Cc: www-style@w3.org
On Thu, Jul 8, 2010 at 2:47 AM, Yuzo Fujishima <yuzo@google.com> wrote: > What unicode normalization (http://unicode.org/reports/tr15/) must be > applied > to the characters in an HTML document before matching against > the unicode-range > descriptor (http://dev.w3.org/csswg/css3-fonts/#unicode-range-desc)? > A. No normalization at all. All the codepoints are checked against > unicode-range as-is. > B. Undefined. Whether to apply normalization is up to UA. > C. Must be normalized to NFC > D. Must be normalized to NFD > E. Must be normalized to NFKC > F. Must be normalize to NFKD > In my opinion, A (or B) is the most realistic choice, seeing that Chrome 6, > Safari 6, IE8, and Opera 10 > don't normalize stylesheets. (Firefox 6 doesn't seem to be working in this > respect.) > http://www.w3.org/International/tests/tests-html-css/tests-normalization/generate?test=10&serveas=xml&format=xhtml5 > Yuzo > Reference: > http://www.w3.org/International/tutorials/tutorial-char-enc/ While I would prefer NFC (the one true normalization form), if *nobody* normalizes right now, then "don't normalize at all" is the pragmatic choice. "Undefined" is not acceptable - it'll result in pages working differently in different browsers. ~TJ
Received on Thursday, 8 July 2010 16:35:19 UTC