Re: [css3-syntax] CSS escape sequences from Boris Zbarsky on 2012-01-12 (www-style@w3.org from January 2012)

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Thu, 12 Jan 2012 09:14:23 -0500
To: Simon Sapin <simon.sapin@kozea.fr>
CC: www-style@w3.org
Message-ID: <4F0EEABF.7080601@mit.edu>

On 1/12/12 8:16 AM, Simon Sapin wrote:
> Isn’t this an accident due to using UCS-2 internally (fixed 16 bits
> encoding) and pretend it is UTF-16? (Or the reverse...)

For what it's worth, Gecko does use UTF-16 internally, but gets this 
right...  It's really not that hard to do.

I do have a question about implementations.  Gecko treats escapes as 
Unicode characters (so in particular escapes in the surrogate ranges are 
treated as invalid and replaced by U+FFFD).  It sounds like WebKit 
treats them as Unicode codepoints, period (no support for direct escapes 
outside the BMP).  What do Presto and Trident actually do?  Do they 
allow both codepoint escapes and character escapes?  Or do they do what 
WebKit does?

-Boris

Received on Thursday, 12 January 2012 14:15:04 UTC