HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
3982Tweaks to handling of bad characters.2009-09-24 09:06
@@ -77305,22 +77305,22 @@ interface <dfn>MessagePort</dfn> {
 
   <p>Given an encoding, the bytes in the input stream must be
   converted to Unicode characters for the tokenizer, as described by
   the rules for that encoding, except that the leading U+FEFF BYTE
   ORDER MARK character, if any, must not be stripped by the encoding
   layer (it is stripped by the rule below).</p> <!-- this is to
   prevent two leading BOMs from being both stripped, once by the
   decoder, and once by the parser -->
 
   <p>Bytes or sequences of bytes in the original byte stream that
-  could not be converted to Unicode characters must be converted to
-  U+FFFD REPLACEMENT CHARACTER code points.</p>
+  could not be converted to Unicode code points must be converted to
+  U+FFFD REPLACEMENT CHARACTERs.</p>
 
   <p class="note">Bytes or sequences of bytes in the original byte
   stream that did not conform to the encoding specification
   (e.g. invalid UTF-8 byte sequences in a UTF-8 input stream) are
   errors that conformance checkers are expected to report.</p>
 
   <p>Any byte or sequences of bytes in the original byte stream that
   is <span>misinterpreted for compatibility</span> is a <span>parse
   error</span>.</p>
 

|