W3C home > Mailing lists > Public > www-style@w3.org > June 2007

Re: [CSS21] out of range unicode escapes

From: fantasai <fantasai.lists@inkedblade.net>
Date: Mon, 11 Jun 2007 12:30:00 -0400
Message-ID: <466D7888.9000803@inkedblade.net>
To: David Clarke <d.r.clarke@sheffield.ac.uk>
CC: "Paul Nelson (ATC)" <paulnel@winse.microsoft.com>, Mark Davis <mark.davis@icu-project.org>, www-style@w3.org, public-i18n-core@w3.org

David Clarke wrote:
> Paul (et Al)
> Following  original discussion by the I18N core;
> I am proposing that  the correct response to any invalid Unicode escape 
> should be to treat it
> as a parse error (see section 4.1.8), in the same way that any other 
> invalid or unexpected character would be.
> This would be consistent with current CSS error handling.
> For clarity Add this text to 4.1.3 at CSS 2.1
> http://www.w3.org/TR/CSS21/syndata.html#q6 
> <http://www.w3.org/TR/CSS21/syndata.html#q6>  :
>     If the number is outside the range allowed by Unicode (e.g.,
>     "\110000" is above the maximum 10FFFF allowed in current Unicode),
>     then the parser should treat this as parse error and A user agent
>     must ignore a declaration containing this invalid property name or
> value.
> see: http://www.w3.org/TR/CSS21/syndata.html#ignore

As Mark pointed out, replacing the invalid Unicode escape with the replacement
character would have that effect anyway, unless it were in a string value such
as for the 'content' property. I think that solution has the advantage of being
much simpler and also doing what we want (making the property declaration etc
invalid) in most cases.

Received on Monday, 11 June 2007 16:30:46 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:29 UTC