The problem I see with this approach is that the document relationship
links in the head section of a page created from an article element
will point to non existing html pages (those created from set, book,
etc). I could of course turn them off but I was hoping there is a
simple fix.
Anyway, thanks Bob.
Robert
On Mon, Feb 14, 2011 at 7:52 PM, Bob Stayton <> wrote:
> Hi,
> The chunking process recursively works through a document to generate
> chunks. So it is not possible to not process at the set, book, and part
> levels, or else their content would not be chunked.
>
> I've found it easier to go ahead and process them, and then discard their
> chunk. You can automate that process by using the dbhtml filename
> processing instruction in each element you want to discard:
>
> http://www.sagehill.net/docbookxsl/Chunking.html#DbhtmlFilenames
>
> and set the filename to "/dev/null" on Linux or "NUL" on Windows.
>
>
>
> Bob Stayton
> Sagehill Enterprises
>
>
>
> ----- Original Message ----- From: "Robert Pasternak" <>
> To: <>
> Sent: Monday, February 14, 2011 1:19 AM
> Subject: [docbook-apps] empty HTML files for set, book, part elements
>
>
>> Dear All
>>
>> My book definition looks like that:
>>
>>
>> <set>
>> <set>
>> <title>set1</title>
>> <book>
>> <title>book1</title>
>> <part>
>> <title>part1</title>
>> <xi:include href="article1.xml"/>
>> <xi:include href="article2.xml"/>
>> </part>
>> </book>
>> <book>
>> <title>book2</title>
>> <part>
>> <title>part2</title>
>> <xi:include href="article3.xml"/>
>> <xi:include href="article4.xml"/>
>> </part>
>> ...
>>
>>
>> I use profile-chunk.xsl with some customization. Please note that
>> included xml files start with the article element. Now, for each set,
>> book, part element the transform produces an html file, basically an
>> empty file with some navigation information. Is it possible to block
>> that behavior so that html files are only produced for article
>> elements?
>>
>> Thanks,
>> Robert
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
>>
>>
>>
>
>
