Hi Marja,
The DocBook stylesheets use the term "chunking" to refer to the process of
bursting a single document into multiple HTML files. This section of my
online book describes chunking in more detail:
http://www.sagehill.net/docbookxsl/Chunking.html
There are a few stylesheet parameters that can be used to control the
breakpoints for chunking. I believe your problem would be solved by setting
the 'chunk.section.depth' parameter to a higher number than the default
value of 1. Currently only your top level sections are being chunked, and
their chunk contains their subsections. Since you want your subsections to
also be chunks, set chunk.section.depth to 2 or higher, depending on how far
down you want things chunked. Since your stylesheet already sets the
use.id.as.filename param to 1, those lower level chunks will get the
filenames you want.
You might also want to set 'chunk.first.sections' to 1 (default value is 0)
so the first section also gets chunked.
On a different topic, I'm not clear what version of DocBook XSL you are
using here. It is clear from the output style that you are using the
webhelp stylesheet, but when I use View Source on the pages you pointed to,
they include this line:
<meta name="generator" content="DocBook XSL-NS Stylesheets V1.75.2"/>
But webhelp was not included in version 1.75.2. When I look in your
webhelp-id-filename.xsl file, I see this import statement:
<xsl:import
href="http://www.calenco.com/xsl/docbook/ns/webhelp/calenco-webhelp.xsl"; />
which does not tell me what version of DocBook XSL is being used. I'm
concerned that Calenco's NeoDoc might be using a hybrid version, and that
might be the source of future problems that this list would have trouble
providing help with.
The latest released version of webhelp is in DocBook XSL 1.77.1.
Bob Stayton
Sagehill Enterprises
[email protected]
--------------------------------------------------
From: "Marja van Waes" <[email protected]>
Sent: Tuesday, December 04, 2012 1:41 PM
To: <[email protected]>
Subject: Re: [docbook-apps] n00b
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/12/12 21:56, Stefan Seefeld wrote:
On 12/04/2012 03:29 PM, Marja van Waes wrote:
Someone advised me to subscribe to this mailing list, to get the
answers to my questions.
That was good advise. However, merely subscribing isn't enough -
you also need to ask the questions. :-)
Stefan
lol
Danke Dir, Stefan
(Thanks, Stefan)
OK, first question:
we're working on a publication, but either the TOC is horrible, or
pages get wrong names and get merged, while they should be seperate pages.
The TOC should become like the one on the left in the publication
here, with an upper level for pages like MCC-System, and the pages
that MCC-System links to (like "Authentication") one tree-view level
lower
waesvanm.home.xs4all.nl/MCC/content/mcc-system-chapter.html
However, the pages should be seperate like the ones here, and get the
file names they have here:
http://docteam.mageia.nl/en/MCC/content/mcc-system.html
(in a somewhat different order, I now put the pages with the links all
at the beginning, the real order should be like the above example)
So each of the pages Software Management up until Boot should in the
TOC become the parent of each page it links to.
For both publications the attached webhelp-id-filename.xsl was used.
For the publication with the "good" TOC, MCCtest.xml was used
For the publication with the "good" seperate files + filenames,
MCC.xml was used
Any help would be greatly appreciated!
Marja
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJQvm34AAoJEKWubDMI5nEB/8kH/0E11Lm+a0FdI/b+7u4JLU7E
tB9/H15ul+0My/PYv03e/+3FrWi5srMB1TjHJ2sQmm2z1qdWhILdhiAoyEWEPEwj
lmhI2GqwHk1/xsu1jWh/FKWgVnH1WPMvTtQw25JDUuBfiWtNkgpZf3n+f3JdJY8t
XcM6+Ckh5qhxAyV4tw0kcTpGIcf6pX4NIMRRkX8JbbIhrGXMunxaoiW3kIJw1ov/
o1GBO/k1zSyrpfSWfEF/tc+P2lyZNvfZeqTxMOUE/ZFxPJcU4F3nFTXL7lt4epXN
8B4fvRjyGKXh+0eKmVI4avKgpMzEDUX+Rlw1EHkZera6CWM8lNwfvOlCC8UPmoY=
=feIZ
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
