After a good night's sleep I realized that the actual page-master that is
allocated to instantiate a blank page actually doesn't matter, so there is
no issue here. Sorry for creating a scare. I should stop writing emails when
my brain is fuzzy.
I happened to be thinking of the reverse situation, when fo:flow content
_still_ exists, which is not the case here.
It doesn't hurt to be aware of most of what I said, though. :-)
Regards,
Arved
At 12:26 AM 7/9/01 -0300, [EMAIL PROTECTED] wrote:
[ SNIP ]
>3. This third point is related to point 2. The default on
"force-page-count" is
>'auto', and unlike a lot of other properties, this one doesn't mean "don't do
>anything". In fact, 'auto' will result in a forced blank page (in this
>implementation) fairly frequently. You need to account for this by having a
>suitable simple-page-master available, basically one that is identified
with a
>blank-or-not-blank='blank' conditional-page-master-reference, or a default
that
>is effectively the same. If not, I cannot guarantee beautiful behaviour at
the
>moment. Basically you don't want a page-master that tries to pull in fo:flow
>content being used for a blank page. If you have been using page-breaks
you are
>probably already OK with this.
>
>Short fix for point 3: if you have lots of material (direct FO, or XSLT
>stylesheets) change your fo:page-sequences to have a
>force-page-count='no-force'. This will save you from having to deal with
blank
>pages if you don't want to. Again, keep in mind that 'no-force' is NOT the
>default.
[ SNIP ]
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
