This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
Re: Help project structure
- From: Jirka Kosek <jirka at kosek dot cz>
- To: denisb at rational dot com
- Cc: "docbook-apps at lists dot oasis-open dot org" <docbook-apps at lists dot oasis-open dot org>
- Date: Wed, 30 Jan 2002 00:03:57 +0100
- Subject: Re: DOCBOOK-APPS: Help project structure
- References: <3906C56A7BD1F54593344C05BD1374B1053EB486@SUS-MA1IT01>
> denisb@rational.com wrote:
>
> I recently did an htmlhelp project where the project was a book
> and each topic was a chapter. Many people have suggested using
> recursive sections for topics instead of chapters, and I'd like to try
> it. Before I dive in:
>
> - If each topic is a section, what would the content model above it
> look like? People have mentioned article - would the model be
> set/book/article/section, where article represents the help project?
I think that
book/chapter/section or
book/chapter/section/section or
book/chapter/section/.../section
is appropriate.
The depth of sections and their embedding gives you control over ToC
structure.
> - Has anyone tried using recursive sections? Does it work - any
> problems to watch out for?
It works OK. You must set following parameters to get separate topic
from each section:
chunk.first.sections=1
chunk.sections=1
chunk.section.depth=5
Jirka
--
-----------------------------------------------------------------
Jirka Kosek
e-mail: jirka@kosek.cz
http://www.kosek.cz