- From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 27 Sep 2011 19:57:15 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec-author-view
In directory hutz:/tmp/cvs-serv20749
Modified Files:
Overview.html content-models.html form-submission.html
spec.html spec.preprocessed.html
Log Message:
tweak the wording (whatwg r6594)
[updated by splitter]
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/Overview.html,v
retrieving revision 1.1623
retrieving revision 1.1624
diff -u -d -r1.1623 -r1.1624
--- Overview.html 26 Sep 2011 22:57:07 -0000 1.1623
+++ Overview.html 27 Sep 2011 19:57:03 -0000 1.1624
@@ -340,7 +340,7 @@
<h1>HTML5: Edition for Web Authors</h1>
- <h2 class="no-num no-toc" id="editor-s-draft-26-september-2011">Editor's Draft 26 September 2011</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-27-september-2011">Editor's Draft 27 September 2011</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/html5-author/">http://www.w3.org/TR/html5-author/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -362,7 +362,7 @@
<dt>Editor:</dt>
<dd><a href="mailto:ian@hixie.ch">Ian Hickson</a>, Google, Inc.</dd>
</dl><p>This specification is available in the following formats: <a href="spec.html">single page HTML</a>, <a href="Overview.html">multipage HTML</a>, <a href="http://dev.w3.org/html5/spec/">full specification</a>.
- This is revision 1.5285.</p>
+ This is revision 1.5288.</p>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
© 2011 <a href="http://www.w3.org/"><abbr title="World Wide
Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts
@@ -513,7 +513,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 26 September 2011 Editor's Draft.
+ This specification is the 27 September 2011 Editor's Draft.
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
Index: spec.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/spec.html,v
retrieving revision 1.1753
retrieving revision 1.1754
diff -u -d -r1.1753 -r1.1754
--- spec.html 26 Sep 2011 22:57:15 -0000 1.1753
+++ spec.html 27 Sep 2011 19:57:04 -0000 1.1754
@@ -341,7 +341,7 @@
<h1>HTML5: Edition for Web Authors</h1>
- <h2 class="no-num no-toc" id="editor-s-draft-26-september-2011">Editor's Draft 26 September 2011</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-27-september-2011">Editor's Draft 27 September 2011</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/html5-author/">http://www.w3.org/TR/html5-author/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -363,7 +363,7 @@
<dt>Editor:</dt>
<dd><a href="mailto:ian@hixie.ch">Ian Hickson</a>, Google, Inc.</dd>
</dl><p>This specification is available in the following formats: <a href="spec.html">single page HTML</a>, <a href="Overview.html">multipage HTML</a>, <a href="http://dev.w3.org/html5/spec/">full specification</a>.
- This is revision 1.5285.</p>
+ This is revision 1.5288.</p>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
© 2011 <a href="http://www.w3.org/"><abbr title="World Wide
Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts
@@ -514,7 +514,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 26 September 2011 Editor's Draft.
+ This specification is the 27 September 2011 Editor's Draft.
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -4371,8 +4371,8 @@
many cases where an element can be empty legitimately, for example
when it is used as a placeholder which will later be filled in by a
script, or when the element is part of a template and would on most
- pages be filled in but on some pages is not relevant.</p><p><a href="#text-node" id="text-node_5" title="text node">Text nodes</a> must not begin with an
- <i>isolated combining character</i>. <a href="#refsUNICODE">[UNICODE]</a></p><h6 id="sectioning-content-0"><span class="secno">3.2.5.1.3 </span>Sectioning content</h6><p><dfn aria-haspopup="true" id="sectioning-content" role="button" tabindex="0">Sectioning content</dfn> is content that defines the scope
+ pages be filled in but on some pages is not relevant.</p><p><a href="#text-node" id="text-node_5" title="text node">Text nodes</a> and attribute values
+ must not begin with an <i>isolated combining character</i>. <a href="#refsUNICODE">[UNICODE]</a></p><h6 id="sectioning-content-0"><span class="secno">3.2.5.1.3 </span>Sectioning content</h6><p><dfn aria-haspopup="true" id="sectioning-content" role="button" tabindex="0">Sectioning content</dfn> is content that defines the scope
of <a href="#heading-content" id="heading-content_1" title="heading content">headings</a> and <a href="#the-footer-element" id="footer_0" title="footer">footers</a>.</p><ul class="brief category-list"><li><code><a href="#the-article-element" id="article_0">article</a></code></li>
<li><code><a href="#the-aside-element" id="aside_0">aside</a></code></li>
<li><code><a href="#the-nav-element" id="nav_0">nav</a></code></li>
@@ -21031,7 +21031,14 @@
Content-Disposition: form-data; name="q"
fur
-------kYFrd4jNJEgCervE--</pre><h5 id="url-encoded-form-data"><span class="secno">4.10.22.1 </span>URL-encoded form data</h5><p>To decode <code><a href="#application-x-www-form-urlencoded" id="application/x-www-form-urlencoded_4">application/x-www-form-urlencoded</a></code>
+------kYFrd4jNJEgCervE--</pre><h5 id="url-encoded-form-data"><span class="secno">4.10.22.1 </span>URL-encoded form data</h5><p class="note">This form data set encoding is in many ways an
+ aberrant monstrosity, the result of many years of implementation
+ accidents and compromises leading to a set of requirements necessary
+ for interoperability, but in no way representing good design
+ practices. In particular, readers are cautioned to pay close
+ attention to the twisted details involving repeated (and in some
+ cases nested) conversions between character encodings and byte
+ sequences.</p><p>To decode <code><a href="#application-x-www-form-urlencoded" id="application/x-www-form-urlencoded_4">application/x-www-form-urlencoded</a></code>
payloads, the following algorithm should be used. This algorithm
uses as inputs the payload itself, <var title="">payload</var>,
consisting of a Unicode string using only characters in the range
@@ -21105,8 +21112,8 @@
</li>
<li><p>Convert the <var title="">name</var> and <var title="">value</var> strings to their byte representation in
- US-ASCII (i.e. convert the Unicode string to a byte
- string).</p></li>
+ ISO-8859-1 (i.e. convert the Unicode string to a byte string,
+ mapping code points to byte values directly).</p></li>
<li><p>Add a pair consisting of <var title="">name</var> and <var title="">value</var> to <var title="">pairs</var>.</p></li>
@@ -21114,9 +21121,8 @@
<li><p>If any of the name-value pairs in <var title="">pairs</var>
have a name component consisting of the string "<code title="">_charset_</code>" encoded in US-ASCII, and the value
- component of the first such pair is the name of a supported
- character encoding, then let <var title="">encoding</var> be that
- character encoding.</p></li>
+ component of the first such pair, when decoded as US-ASCII, is the
+ name of a supported character encoding, then let <var title="">encoding</var> be that character encoding.</p></li>
<li><p>Convert the name and value components of each name-value
pair in <var title="">pairs</var> to Unicode by interpreting the
Index: spec.preprocessed.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/spec.preprocessed.html,v
retrieving revision 1.605
retrieving revision 1.606
diff -u -d -r1.605 -r1.606
--- spec.preprocessed.html 26 Sep 2011 22:57:20 -0000 1.605
+++ spec.preprocessed.html 27 Sep 2011 19:57:12 -0000 1.606
@@ -357,7 +357,7 @@
<h1>HTML5: Edition for Web Authors</h1>
- <h2 class="no-num no-toc" id="editor-s-draft-26-september-2011">Editor's Draft 26 September 2011</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-27-september-2011">Editor's Draft 27 September 2011</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/html5-author/">http://www.w3.org/TR/html5-author/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -379,7 +379,7 @@
<dt>Editor:</dt>
<dd><a href="mailto:ian@hixie.ch">Ian Hickson</a>, Google, Inc.</dd>
</dl><p>This specification is available in the following formats: <a href="spec.html">single page HTML</a>, <a href="Overview.html">multipage HTML</a>, <a href="http://dev.w3.org/html5/spec/">full specification</a>.
- This is revision 1.5285.</p>
+ This is revision 1.5288.</p>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
© 2011 <a href="http://www.w3.org/"><abbr title="World Wide
Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts
@@ -532,7 +532,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 26 September 2011 Editor's Draft.
+ This specification is the 27 September 2011 Editor's Draft.
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -3946,8 +3946,8 @@
many cases where an element can be empty legitimately, for example
when it is used as a placeholder which will later be filled in by a
script, or when the element is part of a template and would on most
- pages be filled in but on some pages is not relevant.</p><p><a href="#text-node" title="text node">Text nodes</a> must not begin with an
- <i>isolated combining character</i>. <a href="#refsUNICODE">[UNICODE]</a></p><h6 id="sectioning-content-0"><span class="secno">3.2.5.1.3 </span>Sectioning content</h6><p><dfn id="sectioning-content" role="button" tabindex="0" aria-haspopup="true">Sectioning content</dfn> is content that defines the scope
+ pages be filled in but on some pages is not relevant.</p><p><a href="#text-node" title="text node">Text nodes</a> and attribute values
+ must not begin with an <i>isolated combining character</i>. <a href="#refsUNICODE">[UNICODE]</a></p><h6 id="sectioning-content-0"><span class="secno">3.2.5.1.3 </span>Sectioning content</h6><p><dfn id="sectioning-content" role="button" tabindex="0" aria-haspopup="true">Sectioning content</dfn> is content that defines the scope
of <a href="#heading-content" title="heading content">headings</a> and <a href="#the-footer-element" title="footer">footers</a>.</p><ul class="brief category-list"><li><code><a href="#the-article-element">article</a></code></li>
<li><code><a href="#the-aside-element">aside</a></code></li>
<li><code><a href="#the-nav-element">nav</a></code></li>
@@ -20873,7 +20873,14 @@
Content-Disposition: form-data; name="q"
fur
-------kYFrd4jNJEgCervE--</pre><h5 id="url-encoded-form-data"><span class="secno">4.10.22.5 </span>URL-encoded form data</h5><p>To decode <code><a href="#application-x-www-form-urlencoded">application/x-www-form-urlencoded</a></code>
+------kYFrd4jNJEgCervE--</pre><h5 id="url-encoded-form-data"><span class="secno">4.10.22.5 </span>URL-encoded form data</h5><p class="note">This form data set encoding is in many ways an
+ aberrant monstrosity, the result of many years of implementation
+ accidents and compromises leading to a set of requirements necessary
+ for interoperability, but in no way representing good design
+ practices. In particular, readers are cautioned to pay close
+ attention to the twisted details involving repeated (and in some
+ cases nested) conversions between character encodings and byte
+ sequences.</p><p>To decode <code><a href="#application-x-www-form-urlencoded">application/x-www-form-urlencoded</a></code>
payloads, the following algorithm should be used. This algorithm
uses as inputs the payload itself, <var title="">payload</var>,
consisting of a Unicode string using only characters in the range
@@ -20947,8 +20954,8 @@
</li>
<li><p>Convert the <var title="">name</var> and <var title="">value</var> strings to their byte representation in
- US-ASCII (i.e. convert the Unicode string to a byte
- string).</p></li>
+ ISO-8859-1 (i.e. convert the Unicode string to a byte string,
+ mapping code points to byte values directly).</p></li>
<li><p>Add a pair consisting of <var title="">name</var> and <var title="">value</var> to <var title="">pairs</var>.</p></li>
@@ -20956,9 +20963,8 @@
<li><p>If any of the name-value pairs in <var title="">pairs</var>
have a name component consisting of the string "<code title="">_charset_</code>" encoded in US-ASCII, and the value
- component of the first such pair is the name of a supported
- character encoding, then let <var title="">encoding</var> be that
- character encoding.</p></li>
+ component of the first such pair, when decoded as US-ASCII, is the
+ name of a supported character encoding, then let <var title="">encoding</var> be that character encoding.</p></li>
<li><p>Convert the name and value components of each name-value
pair in <var title="">pairs</var> to Unicode by interpreting the
Index: form-submission.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/form-submission.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- form-submission.html 17 Aug 2011 23:57:12 -0000 1.7
+++ form-submission.html 27 Sep 2011 19:57:04 -0000 1.8
@@ -372,7 +372,14 @@
Content-Disposition: form-data; name="q"
fur
-------kYFrd4jNJEgCervE--</pre><h5 id="url-encoded-form-data"><span class="secno">4.10.22.1 </span>URL-encoded form data</h5><p>To decode <code><a href="iana.html#application-x-www-form-urlencoded" id="application/x-www-form-urlencoded_4">application/x-www-form-urlencoded</a></code>
+------kYFrd4jNJEgCervE--</pre><h5 id="url-encoded-form-data"><span class="secno">4.10.22.1 </span>URL-encoded form data</h5><p class="note">This form data set encoding is in many ways an
+ aberrant monstrosity, the result of many years of implementation
+ accidents and compromises leading to a set of requirements necessary
+ for interoperability, but in no way representing good design
+ practices. In particular, readers are cautioned to pay close
+ attention to the twisted details involving repeated (and in some
+ cases nested) conversions between character encodings and byte
+ sequences.<p>To decode <code><a href="iana.html#application-x-www-form-urlencoded" id="application/x-www-form-urlencoded_4">application/x-www-form-urlencoded</a></code>
payloads, the following algorithm should be used. This algorithm
uses as inputs the payload itself, <var title="">payload</var>,
consisting of a Unicode string using only characters in the range
@@ -446,8 +453,8 @@
</li>
<li><p>Convert the <var title="">name</var> and <var title="">value</var> strings to their byte representation in
- US-ASCII (i.e. convert the Unicode string to a byte
- string).</li>
+ ISO-8859-1 (i.e. convert the Unicode string to a byte string,
+ mapping code points to byte values directly).</li>
<li><p>Add a pair consisting of <var title="">name</var> and <var title="">value</var> to <var title="">pairs</var>.</li>
@@ -455,9 +462,8 @@
<li><p>If any of the name-value pairs in <var title="">pairs</var>
have a name component consisting of the string "<code title="">_charset_</code>" encoded in US-ASCII, and the value
- component of the first such pair is the name of a supported
- character encoding, then let <var title="">encoding</var> be that
- character encoding.</li>
+ component of the first such pair, when decoded as US-ASCII, is the
+ name of a supported character encoding, then let <var title="">encoding</var> be that character encoding.</li>
<li><p>Convert the name and value components of each name-value
pair in <var title="">pairs</var> to Unicode by interpreting the
Index: content-models.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/content-models.html,v
retrieving revision 1.589
retrieving revision 1.590
diff -u -d -r1.589 -r1.590
--- content-models.html 26 Sep 2011 22:57:08 -0000 1.589
+++ content-models.html 27 Sep 2011 19:57:03 -0000 1.590
@@ -546,8 +546,8 @@
many cases where an element can be empty legitimately, for example
when it is used as a placeholder which will later be filled in by a
script, or when the element is part of a template and would on most
- pages be filled in but on some pages is not relevant.<p><a href="infrastructure.html#text-node" id="text-node_5" title="text node">Text nodes</a> must not begin with an
- <i>isolated combining character</i>. <a href="references.html#refsUNICODE">[UNICODE]</a><h6 id="sectioning-content-0"><span class="secno">3.2.5.1.3 </span>Sectioning content</h6><p><dfn aria-haspopup="true" id="sectioning-content" role="button" tabindex="0">Sectioning content</dfn> is content that defines the scope
+ pages be filled in but on some pages is not relevant.<p><a href="infrastructure.html#text-node" id="text-node_5" title="text node">Text nodes</a> and attribute values
+ must not begin with an <i>isolated combining character</i>. <a href="references.html#refsUNICODE">[UNICODE]</a><h6 id="sectioning-content-0"><span class="secno">3.2.5.1.3 </span>Sectioning content</h6><p><dfn aria-haspopup="true" id="sectioning-content" role="button" tabindex="0">Sectioning content</dfn> is content that defines the scope
of <a href="#heading-content" id="heading-content_1" title="heading content">headings</a> and <a href="the-footer-element.html#the-footer-element" id="footer_0" title="footer">footers</a>.<ul class="brief category-list"><li><code><a href="the-article-element.html#the-article-element" id="article_0">article</a></code></li>
<li><code><a href="the-aside-element.html#the-aside-element" id="aside_0">aside</a></code></li>
<li><code><a href="the-nav-element.html#the-nav-element" id="nav_0">nav</a></code></li>
Received on Tuesday, 27 September 2011 19:57:23 UTC