[html5] r5598 - [e] (0) Mention Format=Flowed explicitly. Fixing http://www.w3.org/Bugs/Public/s [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2010-10-11 15:12:34 -0700 (Mon, 11 Oct 2010)
New Revision: 5598

Modified:
   complete.html
   index
   source
Log:
[e] (0) Mention Format=Flowed explicitly.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=10954

Modified: complete.html
===================================================================
--- complete.html	2010-10-11 22:02:02 UTC (rev 5597)
+++ complete.html	2010-10-11 22:12:34 UTC (rev 5598)
@@ -61480,8 +61480,9 @@
   of the input stream.</p>
 
   <p>The rules for how to convert the bytes of the plain text document
-  into actual characters are defined in RFC 2046, RFC 2646, and
-  subsequent versions thereof. <a href=#refsRFC2046>[RFC2046]</a> <a href=#refsRFC2646>[RFC2646]</a></p>
+  into actual characters, and the rules for actually rendering the
+  text to the user, are defined in RFC 2046, RFC 2646, and subsequent
+  versions thereof. <a href=#refsRFC2046>[RFC2046]</a> <a href=#refsRFC2646>[RFC2646]</a></p>
 
   <p>The <a href="#document's-character-encoding">document's character encoding</a> must be set to the
   character encoding used to decode the document.</p>
@@ -61510,6 +61511,11 @@
   binding, providing script, giving the document a <code><a href=#the-title-element-0>title</a></code>,
   etc.</p>
 
+  <p class=note>In particular, if the user agent supports the <code title="">Format=Flowed</code> feature of RFC 2646 then the user
+  agent would need to apply extra styling to cause the text to wrap
+  correctly and to handle the quoting feature. This could be performed
+  using, e.g., an XBL binding or a CSS extension.</p>
+
   <p>The <a href=#task-source>task source</a> for the two tasks mentioned in this
   section must be the <a href=#networking-task-source>networking task source</a>.</p>
 

Modified: index
===================================================================
--- index	2010-10-11 22:02:02 UTC (rev 5597)
+++ index	2010-10-11 22:12:34 UTC (rev 5598)
@@ -61460,8 +61460,9 @@
   of the input stream.</p>
 
   <p>The rules for how to convert the bytes of the plain text document
-  into actual characters are defined in RFC 2046, RFC 2646, and
-  subsequent versions thereof. <a href=#refsRFC2046>[RFC2046]</a> <a href=#refsRFC2646>[RFC2646]</a></p>
+  into actual characters, and the rules for actually rendering the
+  text to the user, are defined in RFC 2046, RFC 2646, and subsequent
+  versions thereof. <a href=#refsRFC2046>[RFC2046]</a> <a href=#refsRFC2646>[RFC2646]</a></p>
 
   <p>The <a href="#document's-character-encoding">document's character encoding</a> must be set to the
   character encoding used to decode the document.</p>
@@ -61490,6 +61491,11 @@
   binding, providing script, giving the document a <code><a href=#the-title-element-0>title</a></code>,
   etc.</p>
 
+  <p class=note>In particular, if the user agent supports the <code title="">Format=Flowed</code> feature of RFC 2646 then the user
+  agent would need to apply extra styling to cause the text to wrap
+  correctly and to handle the quoting feature. This could be performed
+  using, e.g., an XBL binding or a CSS extension.</p>
+
   <p>The <a href=#task-source>task source</a> for the two tasks mentioned in this
   section must be the <a href=#networking-task-source>networking task source</a>.</p>
 

Modified: source
===================================================================
--- source	2010-10-11 22:02:02 UTC (rev 5597)
+++ source	2010-10-11 22:12:34 UTC (rev 5598)
@@ -69484,8 +69484,9 @@
   of the input stream.</p>
 
   <p>The rules for how to convert the bytes of the plain text document
-  into actual characters are defined in RFC 2046, RFC 2646, and
-  subsequent versions thereof. <a href="#refsRFC2046">[RFC2046]</a> <a
+  into actual characters, and the rules for actually rendering the
+  text to the user, are defined in RFC 2046, RFC 2646, and subsequent
+  versions thereof. <a href="#refsRFC2046">[RFC2046]</a> <a
   href="#refsRFC2646">[RFC2646]</a></p>
 
   <p>The <span>document's character encoding</span> must be set to the
@@ -69515,6 +69516,12 @@
   binding, providing script, giving the document a <code>title</code>,
   etc.</p>
 
+  <p class="note">In particular, if the user agent supports the <code
+  title="">Format=Flowed</code> feature of RFC 2646 then the user
+  agent would need to apply extra styling to cause the text to wrap
+  correctly and to handle the quoting feature. This could be performed
+  using, e.g., an XBL binding or a CSS extension.</p>
+
   <p>The <span>task source</span> for the two tasks mentioned in this
   section must be the <span>networking task source</span>.</p>