My thought precisely.
Here is a fragment from a stylesheet I wrote to print books (for the
software industry):
<xsl:if test="$showIndex='yes'">
<fo:page-sequence master-reference="index">
<!-- static-content and flow goes here, to define the index pages
-->
</fo:page-sequence>
</xsl:if>
The $showIndex variable gets populated at the top of the stylesheet, based
on an implied (and so not always present) attribute in the XML, thus:
<xsl:variable name="showIndex">
<xsl:choose>
<xsl:when test="book/@showIndex='no'">no</xsl:when>
<xsl:otherwise>yes</xsl:otherwise>
</xsl:choose>
</xsl:variable>
Jay Bryant
Bryant Communication Services
(on contract at Synergistic Solution Technologies)
"J.Pietschmann" <[EMAIL PROTECTED]>
01/27/2005 03:28 PM
Please respond to
[EMAIL PROTECTED]
To
[EMAIL PROTECTED]
cc
Subject
Re: Avoiding Blank Pages When using Multiple Page Sequences
Ram Krishnamoorthi wrote:
> In each of my Page Sequence, I am calling one or two
> XSL Templates. In my case, it is possible that I may
> not have any data to Print in a Page Sequence because
> of the absence of specific tags in the Input XML
> File.I would like to avoid having blank pages in the
> PDF document. Is there any attribute I can specify to
> achieve the same?
You'll have to avoid generating the page sequence at the
XSLT level. One possiblity is to put a test for
the existence of the elements which provide the content
around the code which generates the page sequence.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]