You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by je...@apache.org on 2003/02/01 07:46:52 UTC
cvs commit: xml-forrest/etc DTD_DEFICIENCIES.txt
jefft 2003/01/31 22:46:52
Modified: etc DTD_DEFICIENCIES.txt
Log:
Note that <ul>'s can be nested
Revision Changes Path
1.7 +31 -2 xml-forrest/etc/DTD_DEFICIENCIES.txt
Index: DTD_DEFICIENCIES.txt
===================================================================
RCS file: /home/cvs/xml-forrest/etc/DTD_DEFICIENCIES.txt,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- DTD_DEFICIENCIES.txt 8 Jan 2003 05:44:32 -0000 1.6
+++ DTD_DEFICIENCIES.txt 1 Feb 2003 06:46:52 -0000 1.7
@@ -215,6 +215,35 @@
2) Would characters in the included non-XML fragment need to be escaped on rendition? Is this
to show sourcecode fragments or to include in-place verbatim HTML...?
3) Check what Eliotte R. Harold does w.r.t. XInclude (I remember him mentioning this once)
-
+
+
+
+
+ 8) Restrict content of <ul> to <li>
+------------------------------------
+Submittor: Jeff Turner
+Date: 2003-02-01
+Yeas: jefft
+Nays:
+Summary:
+
+Strangely, our docv11 DTD allows lists to be nested in HTML-invalid ways:
+
+<!ENTITY % lists "ol|ul|dl">
+<!ELEMENT li (%content.mix; | %lists;)*>
+
+allowing things like:
+
+<ul>
+ <ul>
+ <ul>
+ <li>Hello</li>
+ </ul>
+ </ul>
+</ul>
+
+In document-v12.dtd, we should restrict the contents of <ul> to just <li>, as
+the HTML DTD does.
+
--
$Revision$ $Date$