html5/html4-differences Overview.src.html,1.163,1.164

Update of /sources/public/html5/html4-differences
In directory hutz:/tmp/cvs-serv2895

Modified Files:
	Overview.src.html 
Log Message:
more xrefs

Index: Overview.src.html
===================================================================
RCS file: /sources/public/html5/html4-differences/Overview.src.html,v
retrieving revision 1.163
retrieving revision 1.164
diff -u -d -r1.163 -r1.164
--- Overview.src.html	6 Mar 2012 12:03:11 -0000	1.163
+++ Overview.src.html	6 Mar 2012 12:04:56 -0000	1.164
@@ -1826,26 +1826,31 @@
     allowed as children (or descendants) of a certain element.
 
     <p>At a high level, HTML4 had two major categories of elements, "inline"
-    (e.g. <code>span</code>, <code>img</code>, text), and "block-level" (e.g.
-    <code>div</code>, <code>hr</code>, <code>table</code>). Some elements did
-    not fit in either category.
+    (e.g. <code data-anolis-spec=html>span</code>, <code
+    data-anolis-spec=html>img</code>, text), and "block-level" (e.g. <code
+    data-anolis-spec=html>div</code>, <code data-anolis-spec=html>hr</code>,
+    <code data-anolis-spec=html>table</code>). Some elements did not fit in
+    either category.
 
-    <p>Some elements allowed "inline" elements (e.g. <code>p</code>), some
-    allowed "block-level" elements (e.g. <code>body</code>, some allowed both
-    (e.g. <code>div</code>), while other elements did not allow either category
-    but only allowed other specific elements (e.g. <code>dl</code>,
-    <code>table</code>), or did now allow any children at all (e.g.
-    <code>link</code>, <code>img</code>, <code>hr</code>).
+    <p>Some elements allowed "inline" elements (e.g. <code
+    data-anolis-spec=html>p</code>), some allowed "block-level" elements (e.g.
+    <code data-anolis-spec=html>body</code>, some allowed both (e.g. <code
+    data-anolis-spec=html>div</code>), while other elements did not allow either
+    category but only allowed other specific elements (e.g. <code
+    data-anolis-spec=html>dl</code>, <code data-anolis-spec=html>table</code>),
+    or did now allow any children at all (e.g. <code
+    data-anolis-spec=html>link</code>, <code data-anolis-spec=html>img</code>,
+    <code data-anolis-spec=html>hr</code>).
 
     <p class=note>Notice the difference between an element itself being in a
     certain category, and having a content model of a certain category. For
-    instance, the <code>p</code> element is itself a "block-level" element, but
-    has a content model of "inline".
+    instance, the <code data-anolis-spec=html>p</code> element is itself a
+    "block-level" element, but has a content model of "inline".
 
     <p>To make it more confusing, HTML4 had different content model rules in its
     Strict, Transitional and Frameset flavors. For instance, in Strict, the
-    <code>body</code> element allowed only "block-level" elements, but in
-    Transitional, it allowed both "inline" and "block-level".
+    <code data-anolis-spec=html>body</code> element allowed only "block-level"
+    elements, but in Transitional, it allowed both "inline" and "block-level".
 
     <p>To make things more confusing still, CSS uses the terms "block-level
     element" and "inline-level element" for its visual formatting model, which
@@ -1854,8 +1859,9 @@
 
     <p>HTML5 does not use the terms "block-level" or "inline" as part of its
     content model rules, to reduce confusion with CSS. However, it has more
-    <span data-anolis-spec=html title="content categories">categories</span> than
-    HTML4, and an element can be part of none of them, one of them, or several of them.
+    <span data-anolis-spec=html title="content categories">categories</span>
+    than HTML4, and an element can be part of none of them, one of them, or
+    several of them.
     
     <ul>
       <li>Metadata content, e.g. <code data-anolis-spec=html>link</code> and

Received on Tuesday, 6 March 2012 12:05:11 UTC