- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Tue, 23 Oct 2012 17:06:37 -0700
- To: Glenn Adams <glenn@skynav.com>
- Cc: Boris Zbarsky <bzbarsky@mit.edu>, www-style@w3.org
On Tue, Oct 23, 2012 at 5:03 PM, Glenn Adams <glenn@skynav.com> wrote: > i'll need to look at the actual language you drafted, but sounds good in > general Just two changes. The "Preprocessing the input stream" section now reads, in part: > Before sending the input stream to the tokenizer, implementations > must make the following character substitutions: > > * Replace any U+000D CARRIAGE RETURN (CR) characters or > pairs of U+000D CARRIAGE RETURN (CR) followed by U+000A > LINE FEED (LF) by a single U+000A LINE FEED (LF) character. > * Replace any U+0000 NULL characters with U+FFFD > REPLACEMENT CHARACTER (�). The "Consume an escaped character" section now reads, in part: > Interpret the hex digits as a hexadecimal number. If this number is > zero, or is greater than the maximum allowed codepoint, return > U+FFFD REPLACEMENT CHARACTER (�). Otherwise, return > the character with that codepoint. ~TJ
Received on Wednesday, 24 October 2012 00:07:26 UTC