[html5] r7160 - [giow] (0) Require an encoding declaration. Affected topics: HTML
whatwg at whatwg.org
whatwg at whatwg.org
Fri Jun 29 13:42:39 PDT 2012
Author: ianh
Date: 2012-06-29 13:42:38 -0700 (Fri, 29 Jun 2012)
New Revision: 7160
Modified:
complete.html
index
source
Log:
[giow] (0) Require an encoding declaration.
Affected topics: HTML
Modified: complete.html
===================================================================
--- complete.html 2012-06-29 01:23:36 UTC (rev 7159)
+++ complete.html 2012-06-29 20:42:38 UTC (rev 7160)
@@ -15660,17 +15660,21 @@
the other is <meta charset>, and the encoding is UTF-8. -->
<p>If an <a href=#html-documents title="HTML documents">HTML document</a> does not
- start with a BOM, and if its encoding is not explicitly given by
- <a href=#content-type title=Content-Type>Content-Type metadata</a>, and the
- document is not <a href=#an-iframe-srcdoc-document>an <code>iframe</code> <code title=attr-iframe-srcdoc>srcdoc</code> document</a>, then the
+ start with a BOM, and its encoding is not explicitly given by <a href=#content-type title=Content-Type>Content-Type metadata</a>, and the document
+ is not <a href=#an-iframe-srcdoc-document>an <code>iframe</code> <code title=attr-iframe-srcdoc>srcdoc</code> document</a>, then the
character encoding used must be an <a href=#ascii-compatible-character-encoding>ASCII-compatible character
- encoding</a>, and, in addition, if that encoding isn't US-ASCII
- itself, then the encoding must be specified using a
+ encoding</a>, and the encoding must be specified using a
<code><a href=#the-meta-element>meta</a></code> element with a <code title=attr-meta-charset><a href=#attr-meta-charset>charset</a></code> attribute or a
<code><a href=#the-meta-element>meta</a></code> element with an <code title=attr-meta-http-equiv><a href=#attr-meta-http-equiv>http-equiv</a></code> attribute in the
<a href=#attr-meta-http-equiv-content-type title=attr-meta-http-equiv-content-type>Encoding declaration
state</a>.</p>
+ <p class=note>A character encoding declaration is required (either
+ in the <a href=#content-type title=Content-Type>Content-Type metadata</a> or
+ explicitly in the file) even if the encoding is US-ASCII, because an
+ encoding is needed to process non-ASCII characters entered by the
+ user in forms, in URLs generated by scripts, and so forth.</p>
+
<p>If the document is <a href=#an-iframe-srcdoc-document>an <code>iframe</code> <code title=attr-iframe-srcdoc>srcdoc</code> document</a>, the
document must not have a <a href=#character-encoding-declaration>character encoding
declaration</a>. (In this case, the source is already decoded,
Modified: index
===================================================================
--- index 2012-06-29 01:23:36 UTC (rev 7159)
+++ index 2012-06-29 20:42:38 UTC (rev 7160)
@@ -15660,17 +15660,21 @@
the other is <meta charset>, and the encoding is UTF-8. -->
<p>If an <a href=#html-documents title="HTML documents">HTML document</a> does not
- start with a BOM, and if its encoding is not explicitly given by
- <a href=#content-type title=Content-Type>Content-Type metadata</a>, and the
- document is not <a href=#an-iframe-srcdoc-document>an <code>iframe</code> <code title=attr-iframe-srcdoc>srcdoc</code> document</a>, then the
+ start with a BOM, and its encoding is not explicitly given by <a href=#content-type title=Content-Type>Content-Type metadata</a>, and the document
+ is not <a href=#an-iframe-srcdoc-document>an <code>iframe</code> <code title=attr-iframe-srcdoc>srcdoc</code> document</a>, then the
character encoding used must be an <a href=#ascii-compatible-character-encoding>ASCII-compatible character
- encoding</a>, and, in addition, if that encoding isn't US-ASCII
- itself, then the encoding must be specified using a
+ encoding</a>, and the encoding must be specified using a
<code><a href=#the-meta-element>meta</a></code> element with a <code title=attr-meta-charset><a href=#attr-meta-charset>charset</a></code> attribute or a
<code><a href=#the-meta-element>meta</a></code> element with an <code title=attr-meta-http-equiv><a href=#attr-meta-http-equiv>http-equiv</a></code> attribute in the
<a href=#attr-meta-http-equiv-content-type title=attr-meta-http-equiv-content-type>Encoding declaration
state</a>.</p>
+ <p class=note>A character encoding declaration is required (either
+ in the <a href=#content-type title=Content-Type>Content-Type metadata</a> or
+ explicitly in the file) even if the encoding is US-ASCII, because an
+ encoding is needed to process non-ASCII characters entered by the
+ user in forms, in URLs generated by scripts, and so forth.</p>
+
<p>If the document is <a href=#an-iframe-srcdoc-document>an <code>iframe</code> <code title=attr-iframe-srcdoc>srcdoc</code> document</a>, the
document must not have a <a href=#character-encoding-declaration>character encoding
declaration</a>. (In this case, the source is already decoded,
Modified: source
===================================================================
--- source 2012-06-29 01:23:36 UTC (rev 7159)
+++ source 2012-06-29 20:42:38 UTC (rev 7160)
@@ -16710,13 +16710,12 @@
the other is <meta charset>, and the encoding is UTF-8. -->
<p>If an <span title="HTML documents">HTML document</span> does not
- start with a BOM, and if its encoding is not explicitly given by
- <span title="Content-Type">Content-Type metadata</span>, and the
- document is not <span>an <code>iframe</code> <code
+ start with a BOM, and its encoding is not explicitly given by <span
+ title="Content-Type">Content-Type metadata</span>, and the document
+ is not <span>an <code>iframe</code> <code
title="attr-iframe-srcdoc">srcdoc</code> document</span>, then the
character encoding used must be an <span>ASCII-compatible character
- encoding</span>, and, in addition, if that encoding isn't US-ASCII
- itself, then the encoding must be specified using a
+ encoding</span>, and the encoding must be specified using a
<code>meta</code> element with a <code
title="attr-meta-charset">charset</code> attribute or a
<code>meta</code> element with an <code
@@ -16724,6 +16723,12 @@
<span title="attr-meta-http-equiv-content-type">Encoding declaration
state</span>.</p>
+ <p class="note">A character encoding declaration is required (either
+ in the <span title="Content-Type">Content-Type metadata</span> or
+ explicitly in the file) even if the encoding is US-ASCII, because an
+ encoding is needed to process non-ASCII characters entered by the
+ user in forms, in URLs generated by scripts, and so forth.</p>
+
<p>If the document is <span>an <code>iframe</code> <code
title="attr-iframe-srcdoc">srcdoc</code> document</span>, the
document must not have a <span>character encoding
More information about the Commit-Watchers
mailing list