At 2004-02-05 15:03 -0500, Gina Cicotello wrote:
>My question is about page numbering, which appears in the footer. Our style
>guide says the last page of content, if an odd page, needs to have special
>page numbering, thus:
>The chapter content ends on page 75. The footer on page 75 says "75/(76
You can't do the "(76 blank)" bit because you cannot calculate using page
>In other parts of the manual (frontmatter and rearmatter), the same scenario
>is treated with "75 (Reverse Blank)". Obviously, I'll create several
I've just tried using a combination of page-position="last" and
odd-or-even="odd" to give you what you want, but the
force-page-count="even" makes the even blank page the last page of the page
sequence (I had mistakenly thought the content page would be considered the
last page of the page sequence) so the condition is never considered true.
On closer examination of the spec, I see in 7.25.6 that any forced page at
the end becomes the "last" page in the sequence for the purposes of testing
page position ... so it is, indeed, not possible to test for "next-to-last"
page in the page sequence.
But I hope the XSL committee is listening or you can take the time to send
your requirement to the xsl-editors@...
address. I think you've made a
justification for a "next-to-last" page-position test value (though not
being an implementer I'm not sure what the ramifications are). Wait ...
even that won't help, because just with that you won't be able to say
"next-to-last when last-is-blank", so it is getting too bizarre to try and
So in summary I think you are out of luck and there may not be a concise
addition to propose to the committee for consideration.
>So I need a conditional that determines when the content ends on an odd
Because conditions are processed at transformation time, and your
requirement is only known at formatting time, there is nothing in 1.0 that
can help you.
>and a way to calculate the next (even) page number.
Nope ... no calculations can be done on page numbers.
>This can't be that uncommon.
Unfortunately there are many "common" requirements that just couldn't be
met with XSL-FO 1.0 that will be addressed in future versions. I
understand that had the committee tried to add everything in the first
version, it would never have been released due to feature creep. The first
version was necessary to understand how it was going to be used.
Public courses: sign up for one or both soon to reserve your seat!
Each week: Monday-Wednesday: XSLT/XPath; Thursday-Friday: XSL-FO
Washington, DC: 2004-03-15 San Francisco, CA: 2004-03-22
Hong Kong, China: 2004-05-17 Bremen, Germany: 2004-05-24
World-wide on-site corporate, government & user group XML training
G. Ken Holman mailto:gkholman@...
Crane Softwrights Ltd. http://www.CraneSoftwrights.com/f/
Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995)
Male Breast Cancer Awareness http://www.CraneSoftwrights.com/f/bc