[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: DOCBOOK-APPS: pernicious mixed content
On Sat, Apr 20, 2002 at 06:42:12PM -0700, Bob Stayton wrote: > The content model for <para> includes #PCDATA, which means > any white space is significant. The stylesheet should pass > any white space through to the output. > > What happens to the white space then depends on the > viewing application. How are you processing your > content? <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> <chapter> <title>A chapter</title> <itemizedlist> <listitem><para> Text I like. There's no white space before it in the pdf output. I use DSSSL 1.76, OpenJade 1.3.1, JadeTeX 3.12. </para></listitem> <listitem><para> Text I don't like. The leading space shows up in the pdf output. Filler. Filler. Filler. Filler. Filler. Filler. Filler. Filler. </para></listitem> <listitem> <para>Text I like. However, html/entry.html in TDG says that it's illegal to have a line break before a block element (i.e., between listitem and para). onsgmls 1.5pre5 doesn't list this as error, though. Where is the truth?</para> </listitem> </itemizedlist> <para> Text I like, no white space. But if all white space in #PCDATA is important, why the leading space of this paragraph is not shown in the pdf output? </para> </chapter> Regards, Baurjan.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC