[html5] r3386 - [e] (0) Allude to consequences of non-UTF-8 encodings.

[whatwg at whatwg.org]

Author: ianh
Date: 2009-07-10 15:09:38 -0700 (Fri, 10 Jul 2009)
New Revision: 3386

Modified:
   index
   source
Log:
[e] (0) Allude to consequences of non-UTF-8 encodings.

Modified: index
===================================================================
--- index	2009-07-10 05:28:51 UTC (rev 3385)
+++ index	2009-07-10 22:09:38 UTC (rev 3386)
@@ -10660,9 +10660,17 @@
   <p>Authors are encouraged to use UTF-8. Conformance checkers may
   advise against authors using legacy encodings.</p>
 
+  <div class=impl>
+
   <p>Authoring tools should default to using UTF-8 for newly-created
   documents.</p>
 
+  </div>
+
+  <p class=note>Using non-UTF-8 encodings can have unexpected
+  results on form submission and URL encodings, which use the
+  <a href="#document's-character-encoding">document's character encoding</a> by default.</p>
+
   <p>In XHTML, the XML declaration should be used for inline character
   encoding information, if necessary.</p>
 

Modified: source
===================================================================
--- source	2009-07-10 05:28:51 UTC (rev 3385)
+++ source	2009-07-10 22:09:38 UTC (rev 3386)
@@ -11167,9 +11167,17 @@
   <p>Authors are encouraged to use UTF-8. Conformance checkers may
   advise against authors using legacy encodings.</p>
 
+  <div class="impl">
+
   <p>Authoring tools should default to using UTF-8 for newly-created
   documents.</p>
 
+  </div>
+
+  <p class="note">Using non-UTF-8 encodings can have unexpected
+  results on form submission and URL encodings, which use the
+  <span>document's character encoding</span> by default.</p>
+
   <p>In XHTML, the XML declaration should be used for inline character
   encoding information, if necessary.</p>