[html5] r3853 - [e] (0) Add note about why we strip all BOMs.

[whatwg at whatwg.org]

Author: ianh
Date: 2009-09-14 21:06:00 -0700 (Mon, 14 Sep 2009)
New Revision: 3853

Modified:
   index
   source
Log:
[e] (0) Add note about why we strip all BOMs.

Modified: index
===================================================================
--- index	2009-09-15 01:44:51 UTC (rev 3852)
+++ index	2009-09-15 04:06:00 UTC (rev 3853)
@@ -62089,6 +62089,12 @@
   <p>One leading U+FEFF BYTE ORDER MARK character must be ignored if
   any are present.</p>
 
+  <p class=note>The requirement to strip a U+FEFF BYTE ORDER MARK
+  character regardless of whether that character was used to determine
+  the byte order is a <a href=#willful-violation>willful violation</a> of Unicode,
+  motivated by a desire to increase the resilience of user agents in
+  the face of naïve transcoders.</p>
+
   <p>All U+0000 NULL characters in the input must be replaced by
   U+FFFD REPLACEMENT CHARACTERs. Any occurrences of such characters is
   a <a href=#parse-error>parse error</a>.</p>

Modified: source
===================================================================
--- source	2009-09-15 01:44:51 UTC (rev 3852)
+++ source	2009-09-15 04:06:00 UTC (rev 3853)
@@ -76644,6 +76644,12 @@
   <p>One leading U+FEFF BYTE ORDER MARK character must be ignored if
   any are present.</p>
 
+  <p class="note">The requirement to strip a U+FEFF BYTE ORDER MARK
+  character regardless of whether that character was used to determine
+  the byte order is a <span>willful violation</span> of Unicode,
+  motivated by a desire to increase the resilience of user agents in
+  the face of naïve transcoders.</p>
+
   <p>All U+0000 NULL characters in the input must be replaced by
   U+FFFD REPLACEMENT CHARACTERs. Any occurrences of such characters is
   a <span>parse error</span>.</p>