[html5] r899 - /

[whatwg at whatwg.org]

Author: ianh
Date: 2007-06-14 18:20:28 -0700 (Thu, 14 Jun 2007)
New Revision: 899

Modified:
   index
   source
Log:
[] (0) Make the networking and parsing sections consistently vague about how to handle bogus bytes.

Modified: index
===================================================================
--- index	2007-06-15 01:00:23 UTC (rev 898)
+++ index	2007-06-15 01:20:28 UTC (rev 899)
@@ -30915,8 +30915,8 @@
    U+000D CARRIAGE RETURN (CR) character. User agents must treat those three
    variants as equivalent line terminators.
 
-  <p>Bytes that are not valid UTF-8 sequences must be interpreted as the
-   U+FFFD REPLACEMENT CHARACTER.
+  <p>Bytes or sequences of bytes that are not valid UTF-8 sequences must be
+   interpreted as the U+FFFD REPLACEMENT CHARACTER.
 
   <p>A leading U+FEFF BYTE ORDER MARK character must be ignored if present.
 

Modified: source
===================================================================
--- source	2007-06-15 01:00:23 UTC (rev 898)
+++ source	2007-06-15 01:20:28 UTC (rev 899)
@@ -28444,8 +28444,8 @@
   character. User agents must treat those three variants as equivalent
   line terminators.</p>
 
-  <p>Bytes that are not valid UTF-8 sequences must be interpreted as
-  the U+FFFD REPLACEMENT CHARACTER.</p>
+  <p>Bytes or sequences of bytes that are not valid UTF-8 sequences
+  must be interpreted as the U+FFFD REPLACEMENT CHARACTER.</p>
 
   <p>A leading U+FEFF BYTE ORDER MARK character must be ignored if
   present.</p>