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: Chunking question


Customizing the chunking to the extent you appear to want is quite
difficult, especially if you want to maintain reasonable previous/next/up
links in the output.  I had a project where I was converting a set of
documentation from HTML into DocBook, and one of my requirements that the
chunking remained the same as it was in the original.  Well, in the
original, the authors didn't follow any rules in chunking, so there are
places where I needed to chunk five sections deep and others where there
were only two, but that second level did have what would be considered
sub-sections.

What I did (and it breaks a few rules of structured editing), was to set the
chunk.section.depth parameter high enough that any section-type element
would chunk.  I then used <bridgehead/> elements to create sub-sections
within a chunk.  It's not a perfect solution.  In fact, I'm not a big fan of
it myself.  However, it does give the author very explicit control of where
to break the HTML pages.

Jeff Beal

-----Original Message-----
From: Roel Vanhout [mailto:roel@riks.nl]
Sent: Monday, January 13, 2003 1:42 PM
To: docbook-apps@lists.oasis-open.org
Subject: DOCBOOK-APPS: Chunking question


Hello all,

I'd like to represent something like this:

- Integrated model
     |-  Model A
         |- Submodel A
         |    |- Submodel Property A
         |    |- Submodel Property B
         |- Submodel B
         |     |- Submodel Property C
         |- Model Property A
         |- Model Property B

I managed to do this with <sect1>, <sect2> & <sect3> tags, and then I 
set the "chunk.section.depth" and "chunk.first.sections" parameters to 
"2" and "1" respectively. The submodels and the model in the example are 
actually similar in what properties they have; how they relate to one 
another depends on how the integrated model is constructed.

Now, I'd like to chunk the data so that all the properties of submodel A 
appear on one page, all the properties of submodel B appear on another 
page and all the properties of model A on a third page. But with 
chunk.section.depth set to 2, Model Property A and Model Propery B are 
chunked to seperate pages. How can I solve this? Can I configure it with 
parameters? Do I need to change the stylesheets? If so, would it be 
hard? Where should I start? I hope I explained my problem clearly 
enough; thanks in advance for all hints.

cheers,

roel


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


Powered by eList eXpress LLC