Subject: Pernicious Mixed Content [was Re: i] From: Norman Walsh <norm@xxxxxxxxxxxxx> Date: Thu, 26 Feb 1998 07:10:09 -0500 |
/ Christian Leutloff <leutloff@xxxxxxxxxxxxxxxxx> was heard to say: [...] | I want to use an itemized list inside a table. This can be done, as | mentionend in the DocBook documentation: [...] | <---------------- | <!DOCTYPE table PUBLIC "-//Davenport//DTD DocBook V3.0//EN"> | <table> | <title>Table with itemizedlist</title> | <tgroup cols=1> | <tbody> | <row> | <entry> | <itemizedlist> | <listitem>first</listitem> | <listitem>second</listitem> | <itemizedlist> | </entry> | </row> | </tbody> | </tgroup> | </table> | <---------------- [...] | What's wrong!? Table Entrys in DocBook exhibit pernicious mixed content. Entrys can contain _either_ PCDATA or block elements (Paras, ItemizedLists, etc.), but not both. Basically, the SGML parser sees the space (or newline) after the <entry> start tag and concludes that this Entry element will contain PCDATA. Four characters later it encounters an ItemizedList which is not allowed. The fix is to remove all spaces after <entry> and before </entry>: <entry><itemizedlist> <listitem><para>first</para></listitem> <listitem><para>second</para></listitem> <itemizedlist></entry> --norm DSSSList info and archive: http://www.mulberrytech.com/dsssl/dssslist
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
i, Christian Leutloff | Thread | Re: Pernicious Mixed Content [was R, Christian Leutloff |
i, Christian Leutloff | Date | Keeping Text Together, Chuck Darney |
Month |