- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 10 Jul 2009 22:09:47 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv20714
Modified Files:
Overview.html
Log Message:
Allude to consequences of non-UTF-8 encodings. (whatwg r3386)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2516
retrieving revision 1.2517
diff -u -d -r1.2516 -r1.2517
--- Overview.html 10 Jul 2009 05:28:57 -0000 1.2516
+++ Overview.html 10 Jul 2009 22:09:44 -0000 1.2517
@@ -9445,8 +9445,14 @@
<a href="#references">[SCSU]</a>
<!-- no idea what to reference for EBCDIC, so... -->
<p>Authors are encouraged to use UTF-8. Conformance checkers may
- advise against authors using legacy encodings.<p>Authoring tools should default to using UTF-8 for newly-created
- documents.<p>In XHTML, the XML declaration should be used for inline character
+ advise against authors using legacy encodings.<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>In XHTML, the XML declaration should be used for inline character
encoding information, if necessary.<h4 id="the-style-element"><span class="secno">4.2.6 </span>The <dfn><code>style</code></dfn> element</h4><dl class="element"><dt>Categories</dt>
<dd><a href="#metadata-content-0">Metadata content</a>.</dd>
<dd>If the <code title="attr-style-scoped"><a href="#attr-style-scoped">scoped</a></code> attribute is present: <a href="#flow-content-0">flow content</a>.</dd>
Received on Friday, 10 July 2009 22:09:57 UTC