hixie: Update the syntax section to more correctly handle newlines. (whatwg r3858)

hixie: Update the syntax section to more correctly handle newlines.
(whatwg r3858)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3023&r2=1.3024&f=h
http://html5.org/tools/web-apps-tracker?from=3857&to=3858

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3023
retrieving revision 1.3024
diff -u -d -r1.3023 -r1.3024
--- Overview.html 15 Sep 2009 08:16:35 -0000 1.3023
+++ Overview.html 15 Sep 2009 08:41:01 -0000 1.3024
@@ -55109,14 +55109,14 @@
   <code><a href="#the-table-element">table</a></code> elements according to the content models
   described in this specification. (If a <code><a href="#the-tr-element">tr</a></code> element is
   put inside a <code><a href="#the-table-element">table</a></code> in the markup, it will in fact imply
-  a <code><a href="#the-tbody-element">tbody</a></code> start tag before it.)<p>A single U+000A LINE FEED (LF) character may be placed
-  immediately after the <a href="#syntax-start-tag" title="syntax-start-tag">start
+  a <code><a href="#the-tbody-element">tbody</a></code> start tag before it.)<p>A single <a href="#syntax-newlines" title="syntax-newlines">newline</a> may be
+  placed immediately after the <a href="#syntax-start-tag" title="syntax-start-tag">start
   tag</a> of <code><a href="#the-pre-element">pre</a></code> and <code><a href="#the-textarea-element">textarea</a></code>
   elements. This does not affect the processing of the element. The
-  otherwise optional U+000A LINE FEED (LF) character <em>must</em> be
-  included if the element's contents start with that character
-  (because otherwise the leading newline in the contents would be
-  treated like the optional newline, and ignored).<div class="example">
+  otherwise optional <a href="#syntax-newlines" title="syntax-newlines">newline</a>
+  <em>must</em> be included if the element's contents start with that
+  character (because otherwise the leading newline in the contents
+  would be treated like the optional newline, and ignored).<div class="example">
    <p>The following two <code><a href="#the-pre-element">pre</a></code> blocks are equivalent:</p>
    <pre>&lt;pre&gt;Hello&lt;/pre&gt;</pre>
    <pre>&lt;pre&gt;<br>Hello&lt;/pre&gt;</pre>
@@ -55125,8 +55125,10 @@
   LESS-THAN SIGN, U+002F SOLIDUS) followed by characters that
   case-insensitively match the tag name of the element followed by one
   of U+0009 CHARACTER TABULATION, U+000A LINE FEED (LF), U+000C FORM
-  FEED (FF), U+0020 SPACE, U+003E GREATER-THAN SIGN (&gt;), or U+002F
-  SOLIDUS (/), unless that string is part of an <a href="#syntax-escape" title="syntax-escape">escaping text span</a>.<p>An <dfn id="syntax-escape" title="syntax-escape">escaping text span</dfn> is a span
+  FEED (FF), U+000D CARRIAGE RETURN (CR), U+0020 SPACE, U+003E
+  GREATER-THAN SIGN (&gt;), or U+002F SOLIDUS (/), unless that string is
+  part of an <a href="#syntax-escape" title="syntax-escape">escaping text
+  span</a>.<p>An <dfn id="syntax-escape" title="syntax-escape">escaping text span</dfn> is a span
   of <a href="#syntax-text" title="syntax-text">text</a> that starts with an <a href="#syntax-escape-start" title="syntax-escape-start">escaping text span start</a> that is
   not itself in an <a href="#syntax-escape" title="syntax-escape">escaping text
   span</a>, and ends at the next <a href="#syntax-escape-end" title="syntax-escape-end">escaping text span end</a>. There
@@ -59457,10 +59459,10 @@
     <div class="example">
      <p class="XXX">Need an example.</p>
     </div>
---><p class="note">Because of the way this algorithm causes elements to
-    change parents, it has been dubbed the "adoption agency algorithm"
-    (in contrast with other possibly algorithms for dealing with
-    misnested content, which included the "incest algorithm", the
+--><p class="note">Because of the way this algorithm causes elements
+    to change parents, it has been dubbed the "adoption agency
+    algorithm" (in contrast with other possible algorithms for dealing
+    with misnested content, which included the "incest algorithm", the
     "secret affair algorithm", and the "Heisenberg algorithm").</p>
 
    </dd>

Received on Tuesday, 15 September 2009 08:41:57 UTC