This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
[docbook-apps] simplesect ends up fully in content page
- From: Tom Peters <tom at tompth dot xs4all dot nl>
- To: docbook-apps at lists dot oasis-open dot org
- Date: Thu, 13 Jan 2005 22:25:25 +0100 (CET)
- Subject: [docbook-apps] simplesect ends up fully in content page
Currently I have the situation that the full content of simplesect blocks
is rendered into the table of contents under the heading of the embracing
chapter. Exactly the same DocBook xml code was processed correctly in the
first half of 2004.
Any suggestions?
Currently I am using xsltproc 1.0.33, and docbook-xsl 1.66.1
My processing:
#!/bin/sh
#
xsltproc -o GemBook.tmp add-indexterms.xsl GemBook.xml
xsltproc -o mytitlepage.xsl \
/usr/share/xml/docbook/stylesheet/nwalsh/template/titlepage.xsl \
mytitlepage.xml
xsltproc -o GemBook.fo --stringparam paper.type A4 print.xsl GemBook.tmp
fop GemBook.fo GemBook.pdf
The first step makes indexterms of glossterms so that they end up in the
index. I use a stylesheet that someone kindly provided when I asked
aboutthe proper procedure on this list sometime last year.
The second step prepares a titlepage using a customized version of
Walsh's standard template.
The print.xsl includes the titlepage.
GemBook.xml does nothing more than describe bookinfo and include several
parts, the first of which is now problematic:
<chapter>
<title>Inleiding</title>
<simplesect>
<title>Onderwerp</title>
<para>
whatever
</para>
</simplesect>
<simplesect>
<title>De cursus is onderverdeeld in drie secties</title>
<orderedlist numeration="upperalpha">
...listitems...
</orderedlist>
</simplesect>
</chapter>
--
#>!$!%(@^%#%*(&(#@#*$^@^$##*#@&(%)@**$!(&!^(#((#&%!)%*@)(&$($$%(@#)&*!^$)^@*^@)
Tom Peters