At 2006-03-25 23:05 -0700, Jordan (Wraezor) wrote:
I got it sort of working, however, instead of being truly blank, like I
want, it is including the header and footer like the rest of the pages.
I suspect what's happening is it's not using the blank page, but instead
is just continuing on with the Left/Right pages.
Correct, given the code fragment you cited.
However, oddly enough,
when FOP (0.20.5) completes the PDF generation,
I cannot comment specifically on FOP behaviour ... sorry.
it does label the
appropriate pages as "(blank)" in its output....but they'll still contain
a header and footer, just no flow.
Looking at your page geometry, I don't see why it would do that.
So, my question is...how can I retain the same behaviour (insert blank
were needed), but also make it strip off the static-content that it seems
to want to retain. It seems it never calls the Blank
simple-page-master...and I don't know why.
Any ideas?
Because of the order of your alternatives.
My page-sequence-master is as follows:
<fo:page-sequence-master master-name="chapter">
<fo:repeatable-page-master-alternatives>
<fo:conditional-page-master-reference master-reference="ChapterFirst"
page-position="first"/>
<fo:conditional-page-master-reference master-reference="BodyLeft"
odd-or-even="even"/>
<fo:conditional-page-master-reference master-reference="BodyRight"
odd-or-even="odd"/>
<fo:conditional-page-master-reference master-reference="Blank"
blank-or-not-blank="blank" />
</fo:repeatable-page-master-alternatives>
</fo:page-sequence-master>
When an XSL-FO processor needs a new page geometry from the sequence
of geometries, it walks through each conditional reference *in
document order of the alternatives*, finding the first reference
whose properties match the properties of the page being formatted and
then stops looking. Since you have both choices of page parity
before page blankness, then it will never reach the alternative for
page blankness.
Positioning your fourth reference first will test true for blank
pages before testing true for one of the page parity tests. It is
okay for it to be first in the list for pages with flow because it
will never test true for pages with flow ... but the way you have it
now pages without flow will test true for page parity before they
test true for blankness.
I hope this helps.
. . . . . . . . . . . Ken
--
Registration open for XSLT/XSL-FO training: Wash.,DC 2006-06-12/16
World-wide on-site corporate, govt. & user group XML/XSL training.
G. Ken Holman mailto:gkholman(_at_)CraneSoftwrights(_dot_)com
Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/
Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995)
Male Cancer Awareness Aug'05 http://www.CraneSoftwrights.com/s/bc
Legal business disclaimers: http://www.CraneSoftwrights.com/legal
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--