OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: DOCBOOK-APPS: Help project structure


I never saw a recommendation for using article, so I don't know of the
advantages.  Would like to know if there are any.

First file is the first section as you thought.

I use <sect1>, <sect2>, etc.. for section tags and nesting.  As for
suppressing chunking of subsections, I have no need to do that, but I am
sure you could customize the stylesheet somewhere to do that.

I will have some sections (<sect1>) for which I will not want in my table of
contents.  I am thinking I will check the id for those sections I want
suppressed using a xsl customization so that a .hhc entry isn't generated
for it.  Haven't thought enough about that.  I'm pretty new to all of this
myself, so this is like the blind leading the blind.

Maggie

-----Original Message-----
From: denisb@rational.com [mailto:denisb@rational.com]
Sent: Tuesday, January 29, 2002 12:59 PM
To: docbook-apps@lists.oasis-open.org
Subject: RE: DOCBOOK-APPS: Help project structure


> -----Original Message-----
> From: Maggie Strevell [mailto:maggie@ssinc.com]

>  I am using a section to represent each help topic.  The type
> of driver file (book|chapter|section).

This looks sensible to me. How come some people recommend article instead of
chapter? Is there some advantage I'm missing?

>  <!-- the file name for the first file in this chapter is
> generated using the id for the chapter -->

Does 'first file' mean the first section? With recursive sections, you could
have a topic with subsections like this, right?

   <section>
      content...
      <section>Subsection 1...</section>
      <section>Subsection 2...</section>
      <section>See also...</section>
   </section>

The problem with this scenario is that I don't see how to control chunking:
I'd want the whole structure above to be one topic, chunking only the top
section. Do you know how one would suppress chunking in the subsections?

Thanks,
Denis




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC