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

RE: [I18N Core Response][CSS21] out of range unicode escapes

From: Paul Nelson (ATC) <paulnel@winse.microsoft.com>
Date: Tue, 26 Jun 2007 14:06:00 -0700
Message-ID: <49C257E2C13F584790B2E302E021B6F913B7EE8C@winse-msg-01.segroup.winse.corp.microsoft.com>
To: Addison Phillips <addison@yahoo-inc.com>, <www-style@w3.org>
CC: <member-i18n-core@w3.org>
If the end result is to generate a parser error, does the parsing of the style sheet end immediately and other styles or user defined styles are applied?

If a parser error is generated the procedure for UA behavior must be defined.

Is it better to abort style than to attempt to recover?

How often is this situation encountered? Is it a hypothetical issue, or a real issue?


-----Original Message-----
From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf Of Addison Phillips
Sent: Wednesday, June 27, 2007 4:50 AM
To: www-style@w3.org
Cc: member-i18n-core@w3.org
Subject: [I18N Core Response][CSS21] out of range unicode escapes


I'm writing on behalf of the Internationalization Core Working Group. In 
our most recent teleconference, we discussed this issue again. 
Basically, the options for handling out of range Unicode escapes were:

- do nothing/permit the invalid code point
- replace with U+FFFD
- generate a parse error

The first option is a security risk and shouldn't be seriously 
considered. Either of the other options could potentially be a valid choice.

We note that this issue has to do with an escape sequence representing a 
Unicode character. It shouldn't be associated with transcoding errors 
from legacy encodings, although it could result from a bug in an escape 
generator. That is, such malformed sequences are generated purposefully.

We feel that the best response to this issue is to generate a parse 
error. Use of the replacement character might mask errors in the style 
sheet (since there is no obvious failure or failure location), while it 
is unlikely that the resulting sequence would produce the desired 
stylistic behavior anyway. Therefore, we recommend that the CSS working 
group, for clarity, add this text to 4.1.3 in CSS 2.1 at about


     If the number is outside the range allowed by Unicode (e.g.,
     "\110000" is above 0x10FFFF, the largest Unicode code point),
     then the parser should treat this as a parse error and a user agent
     must ignore any declaration containing this invalid property name
     or value.

Note that this text is slightly revised from a previous proposal.

We welcome any comments you might have on this issue.

Best Regards,


Addison Phillips
Globalization Architect -- Yahoo! Inc.
Chair -- W3C Internationalization Core WG

Internationalization is an architecture.
It is not a feature.

Received on Tuesday, 26 June 2007 21:06:15 UTC

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