W3C home > Mailing lists > Public > public-html-commits@w3.org > April 2011

html5/spec Overview.html,1.4806,1.4807

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 08 Apr 2011 22:12:30 +0000
To: public-html-commits@w3.org
Message-Id: <E1Q8Juo-0000k3-NX@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv2837

Modified Files:
	Overview.html 
Log Message:
apply wg decision (whatwg r5979)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4806
retrieving revision 1.4807
diff -u -d -r1.4806 -r1.4807
--- Overview.html	8 Apr 2011 21:35:48 -0000	1.4806
+++ Overview.html	8 Apr 2011 22:12:26 -0000	1.4807
@@ -575,7 +575,8 @@
     <ol>
      <li><a href="#concept-http-equivalent"><span class="secno">2.7.1 </span>Protocol concepts</a></li>
      <li><a href="#encrypted-http-and-related-security-concerns"><span class="secno">2.7.2 </span>Encrypted HTTP and related security concerns</a></li>
-     <li><a href="#content-type-sniffing"><span class="secno">2.7.3 </span>Determining the type of a resource</a></ol></li>
+     <li><a href="#content-type-sniffing"><span class="secno">2.7.3 </span>Determining the type of a resource</a></li>
+     <li><a href="#extracting-encodings-from-meta-elements"><span class="secno">2.7.4 </span>Extracting encodings from <code>meta</code> elements</a></ol></li>
    <li><a href="#common-dom-interfaces"><span class="secno">2.8 </span>Common DOM interfaces</a>
     <ol>
      <li><a href="#reflecting-content-attributes-in-idl-attributes"><span class="secno">2.8.1 </span>Reflecting content attributes in IDL attributes</a></li>
@@ -6027,9 +6028,12 @@
   occur. For more details, see the Media Type Sniffing
   specification. <a href="#refsMIMESNIFF">[MIMESNIFF]</a></p>
 
-  <p>The <dfn id="algorithm-for-extracting-an-encoding-from-a-content-type">algorithm for extracting an encoding from a
-  Content-Type</dfn>, given a string <var title="">s</var>, is as
-  follows. It either returns an encoding or nothing.</p>
+
+  <h4 id="extracting-encodings-from-meta-elements"><span class="secno">2.7.4 </span>Extracting encodings from <code><a href="#meta">meta</a></code> elements</h4>
+
+  <p>The <dfn id="algorithm-for-extracting-an-encoding-from-a-meta-element">algorithm for extracting an encoding from a
+  <code>meta</code> element</dfn>, given a string <var title="">s</var>, is as follows. It either returns an encoding or
+  nothing.</p>
 
   <ol><!-- http://www.hixie.ch/tests/adhoc/html/parsing/encoding/all.html --><li><p>Let <var title="">position</var> be a pointer into <var title="">s</var>, initially pointing at the start of the
    string.</li>
@@ -6071,13 +6075,14 @@
 
     </dl></li>
 
-  </ol><p class="note">This requirement is a <a href="#willful-violation">willful violation</a>
-  of the HTTP specification (for example, HTTP doesn't allow the use
-  of single quotes and requires supporting a backslash-escape
-  mechanism that is not supported by this algorithm<!-- not to mention
-  not having any rules for error-handling, which is of course why
-  we're having to define it ourselves -->), motivated by the need for
-  backwards compatibility with legacy content. <a href="#refsHTTP">[HTTP]</a></p>
+  </ol><p class="note">This algorithm is distinct from those in the HTTP
+  specification (for example, HTTP doesn't allow the use of single
+  quotes and requires supporting a backslash-escape mechanism that is
+  not supported by this algorithm<!-- not to mention not having any
+  rules for error-handling, which is of course why we're having to
+  define it ourselves -->). While the algorithm is used in contexts
+  that, historically, were related to HTTP, the syntax as supported by
+  implementations diverged some time ago. <a href="#refsHTTP">[HTTP]</a></p>
 
   </div><h3 id="common-dom-interfaces"><span class="secno">2.8 </span>Common DOM interfaces</h3><h4 id="reflecting-content-attributes-in-idl-attributes"><span class="secno">2.8.1 </span>Reflecting content attributes in IDL attributes</h4><p>Some IDL attributes are defined to <dfn id="reflect">reflect</dfn> a
   particular content attribute. This means that on getting, the IDL
@@ -55144,11 +55149,13 @@
 
            <dt>If the attribute's name is "<code title="">content</code>"</dt>
 
-           <dd><p>Apply the <a href="#algorithm-for-extracting-an-encoding-from-a-content-type">algorithm for extracting an encoding
-           from a Content-Type</a>, giving the attribute's value as
-           the string to parse. If an encoding is returned, and if
-           <var title="">charset</var> is still set to null, let <var title="">charset</var> be the encoding returned, and set
-           <var title="">need pragma</var> to true.</dd>
+           <dd><p>Apply the <a href="#algorithm-for-extracting-an-encoding-from-a-meta-element">algorithm for extracting an encoding
+           from a <code>meta</code> element</a>, giving the
+           attribute's value as the string to parse. If an encoding is
+           returned, and if <var title="">charset</var> is still set
+           to null, let <var title="">charset</var> be the encoding
+           returned, and set <var title="">need pragma</var> to
+           true.</dd>
 
            <dt>If the attribute's name is "<code title="">charset</code>"</dt>
 
@@ -59123,10 +59130,10 @@
     value is an <a href="#ascii-case-insensitive">ASCII case-insensitive</a> match for the
     string "<code title="">Content-Type</code>", and the element has a
     <code title="attr-meta-content"><a href="#attr-meta-content">content</a></code> attribute, and
-    applying the <a href="#algorithm-for-extracting-an-encoding-from-a-content-type">algorithm for extracting an encoding from a
-    Content-Type</a> to that attribute's value returns a supported
-    <a href="#ascii-compatible-character-encoding">ASCII-compatible character encoding</a> or a UTF-16
-    encoding, and the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> is currently
+    applying the <a href="#algorithm-for-extracting-an-encoding-from-a-meta-element">algorithm for extracting an encoding from a
+    <code>meta</code> element</a> to that attribute's value returns
+    a supported <a href="#ascii-compatible-character-encoding">ASCII-compatible character encoding</a> or a
+    UTF-16 encoding, and the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> is currently
     <i>tentative</i>, then <a href="#change-the-encoding">change the encoding</a> to the
     extracted encoding.</p>
 
Received on Friday, 8 April 2011 22:12:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 8 April 2011 22:12:34 GMT