- From: Bert Bos <bert@w3.org>
- Date: Mon, 19 Feb 2007 17:18:15 +0100
- To: Undisclosed.Recipients: ;
- Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, www-style@w3.org
On Friday 12 January 2007 16:35, Paul Nelson (ATC) wrote:
> Any data outside the range of valid Unicode is not defined. To be
> consistent with handling bad UTF-8, we should probably specify
> changing it into the replacement character.
>
> Paul
>
> -----Original Message-----
> From: www-style-request@w3.org [mailto:www-style-request@w3.org] On
> Behalf Of Bjoern Hoehrmann Sent: Friday, January 12, 2007 6:52 AM
> To: www-style@w3.org
> Subject: [CSS21] out of range unicode escapes
>
>
> Hi,
>
> The current CSS 2.1 draft does not address handling of Unicode
> escapes that appear to be above U+10FFFF like \FFFFFF. Such a
> sequence could be interpreted as 5-digit escape followed by 'F', or
> be considered invalid, or handled as if it was the replacement
> character \FFFD, or in other ways. Implementations do not agree on
> how to handle this case.
The CSS WG discussed the issue and decided only on the principle that a
UA that displays the character in any way *should* display some visible
symbol, similar to how it should handle legal characters for which no
font is available.
The next draft will contain this paragraph at the end of the 3rd bullet
in 4.1.3 :
If the number is outside the range allowed by Unicode (e.g.,
"\110000" is above the maximum 10FFFF allowed in current Unicode),
the UA may replace the escape with the "replacement character"
(U+FFFD). If the character is to be displayed, the UA should show a
visible symbol, such as a "missing character" glyph (cf. 15.2, point
5).
Please let us know if this solves the issue.
[For reference: we put this issue in the planned "disposition of
comments" document as "issue 19."]
Bert
--
Bert Bos ( W 3 C ) http://www.w3.org/
http://www.w3.org/people/bos W3C/ERCIM
bert@w3.org 2004 Rt des Lucioles / BP 93
+33 (0)4 92 38 76 92 06902 Sophia Antipolis Cedex, France
Received on Monday, 19 February 2007 16:18:39 UTC