- From: Witold Baryluk <baryluk@smp.if.uj.edu.pl>
- Date: Fri, 13 Jan 2012 23:47:21 +0100
- To: Mathias Bynens <mathias@qiwi.be>
- Cc: Jonathan Kew <jonathan@jfkew.plus.com>, www-style <www-style@w3.org>
On 01-12 14:41, Mathias Bynens wrote: > Something like: “If a UTF-16 surrogate > pair is found, decode it as such; else, proceed as usual.” > Why anybody would like to have such functionality? It only makes everybodys lives harder. Just add to the spec, that behaviour when surrogate entries outside BMP will occure, are implementation defined. I think they should convert to 'invalid character' glyph (twice, for each surrogate), and then continue with processing as usual. This makes implementation easier, especially when internally everything is processed using something different than UTF-16 (like unicode code points, UTF-8 or UTF-32, all quite common in some languages). Not only browsers needs to implement CSS processing this days, so keeping implementation and escape rules simpler is good for everyone. Thanks. -- Witold Baryluk
Received on Friday, 13 January 2012 22:47:47 UTC