This is the mail archive of the docbook-apps@lists.oasis-open.org mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Help project structure


> RE: using recursive sections for topics instead of chapters in HTML Help

I've been testing docbook 1.48 (and the latest htmlhelp.xsl from CVS) on the
following help project structure:
<book>
    <chapter>
        <title>Help for My App</title>
	 &topic1;
             &topic2;
       </chapter>
</book>

Previously I maintained the project file and toc by hand because the
generated .hhp and .hhc files were not usable. 1.48 enhances this
automation, but I'm having the following problems with it:

1. htmlhelp.xsl  generates chunks for book and chapter, and also lists them
in FILES section of .hhp project file. What's the best way to NOT generate
these elements and to exclude them from the .hhp project file? I couldn't
get any parameters to do it.

2. When coded this way, the topic structure must be very flat, right?
Suppose I want to end up with nested TOC items like this:

Help for App
     Using App
            Getting started
                  Installing 
                  After installing

Of course, some of the items might be just titles, like the first one, which
is the chapter and has no link. But all actual topics are siblings - 1st
level sections in the chapter - so I'm not sure how to get them to nest in
the generated hhc file, as shown above.

To be honest, neither of these problems is a show stopper for us. The book
and chapter file are just messy, they don't affect anything. And in our last
project it was very easy to maintain the .hhc manually (in HTML Help
Workshop), where the TOC structure can be completely independent of the XML
topic structure. 

Finally, even without the automation, coding all topics as sections enables
us to potentially reuse them. Just thought I'd check with the experts before
I abandon the automation - I'd appreciate any suggestions.
 _____
 Denis


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]