W3C home > Mailing lists > Public > public-html@w3.org > July 2009

Re: Non-character NCRs treated differently from literal non-characters

From: Henri Sivonen <hsivonen@iki.fi>
Date: Thu, 9 Jul 2009 11:55:38 +0300
Cc: "public-html@w3.org WG" <public-html@w3.org>
Message-Id: <596C9EF1-BCC1-4750-90EC-1C13F8A46561@iki.fi>
To: Ian Hickson <ian@hixie.ch>
On Jul 8, 2009, at 04:04, Ian Hickson wrote:

> On Wed, 10 Jun 2009, Henri Sivonen wrote:
>>>>
>>>> But why, then, do non-character NCRs turn into REPLACEMENT
>>>> CHARACTER?
>>>
>>> For consistency.
>>
>> In that case, I suggest letting non-characters end up in the DOM in  
>> both
>> cases as is traditional.
>
> Fixed.


Thanks.

For the C1 range, I see that you sided with IE and WebKit rather than  
Gecko and Opera. Was that intentional? (I didn't mean to ask for  
*that*. :-)

The edit introduced one outright spec bug: Numbers above 0x10FFFF  
should still turn into U+FFFD.

-- 
Henri Sivonen
hsivonen@iki.fi
http://hsivonen.iki.fi/
Received on Thursday, 9 July 2009 08:56:20 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:48 UTC