hixie: typo (whatwg r6660)

hixie: typo (whatwg r6660)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.5339&r2=1.5340&f=h
http://html5.org/tools/web-apps-tracker?from=6659&to=6660

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5339
retrieving revision 1.5340
diff -u -d -r1.5339 -r1.5340
--- Overview.html 11 Oct 2011 00:29:29 -0000 1.5339
+++ Overview.html 11 Oct 2011 22:58:34 -0000 1.5340
@@ -320,7 +320,7 @@
 
    <h1>HTML5</h1>
    <h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
-   <h2 class="no-num no-toc" id="editor-s-draft-10-october-2011">Editor's Draft 10 October 2011</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-11-october-2011">Editor's Draft 11 October 2011</h2>
    <dl><dt>Latest Published Version:</dt>
     <dd><a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a></dd>
     <dt>Latest Editor's Draft:</dt>
@@ -466,7 +466,7 @@
   Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation
   track.
-  This specification is the 10 October 2011 Editor's Draft.
+  This specification is the 11 October 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
@@ -40553,10 +40553,8 @@
   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
-  U+0000 to U+007F; a default character encoding <var title="">default
-  encoding</var>; and optionally an <var title="">isindex</var> flag
-  indicating that the payload is to be processed as if it had been
-  generated for a form containing an <code title="attr-fe-name-isindex"><a href="#attr-fe-name-isindex">isindex</a></code> control. The output of
+  U+0000 to U+007F; a default character encoding <var title="">encoding</var>; and optionally an <var title="">isindex</var> flag indicating that the payload is to be
+  processed as if it had been generated for a form containing an <code title="attr-fe-name-isindex"><a href="#attr-fe-name-isindex">isindex</a></code> control. The output of
   this algorithm is a sorted list of name-value pairs. If the <var title="">isindex</var> flag is set and the first control really was
   an <code title="attr-fe-name-isindex"><a href="#attr-fe-name-isindex">isindex</a></code> control, then
   the first name-value pair will have as its name the empty
@@ -40633,7 +40631,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, when decoded as US-ASCII, is the
-   name of a supported character encoding, then let <var title="">encoding</var> be that character encoding.</li>
+   name of a supported character encoding, then let <var title="">encoding</var> be that character encoding (replacing the
+   default passed to the algorithm).</li>
 
    <li><p>Convert the name and value components of each name-value
    pair in <var title="">pairs</var> to Unicode by interpreting the

Received on Tuesday, 11 October 2011 22:59:02 UTC