Re: [docbook-apps] Parameter refentry.pagebreak makes no effect?

["Bob Stayton" <bobs at sagehill dot net>]

The stylesheet has some interesting logic regarding refentry when inside a
reference (or part) element.  It creates a title page for the reference
element, but that is all it puts in that page sequence.  Each refentry in
the reference element starts a new page sequence.  That is done because only
a page sequence can start on an odd-numbered page, which is a common style
for manual pages.  The refentry.pagebreak parameter doesn't affect this
logic, and so it is only useful when refentry appears inside something other
than a reference or part element.

I consider this is a bug, since the expectation is that the parameter should
join the refentries together.  The parameter needs to be applied earlier in
the template, to create a single page sequence for the reference element so
that the individual refentry elements are not in their individual
page-sequences.

Can you file a bug report on this on the DocBook SourceForge site?

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: "Thomas Schraitle" <tom_schr@web.de>
To: <docbook-apps@lists.oasis-open.org>
Sent: Saturday, April 09, 2005 2:41 AM
Subject: [docbook-apps] Parameter refentry.pagebreak makes no effect?


> Hi,
>
> according to the Stylesheet docs[1] if you set the refentry.pagebreak
> parameter to zero there will be no page break generated between
> refentrys. So far, so good.
>
> As far as I can see, this doesn't work. I tried the latest stylesheets
> from [2] but with no success. If I look into the Bug tracking system and
> search for refentry I get no results.
>
> I looked also in the fo/refentry.xsl for template refentry but I don't see
> any obvious error.
>
> Is this really a bug or do I miss something. Any hints?
>
> Thanks,
> Tom
>
> ------------
> [1]
>
http://docbook.sourceforge.net/release/xsl/current/doc/fo/refentry.pagebreak.html
> [2] http://docbook.sourceforge.net/snapshots/
>
> -- 
> Thomas Schraitle <tom_schr@web.de>
>
>