Thanks for all the responses
I have bundled my replies in one message
The processor is Antenna House.
The process is part of a complex customisation on top of the Dita OT.
So prior than starting to look for unwanted effects and breaks
allover the code,
I wanted to make sure this is not a known bug in any processor, or an
expected behaviour
Now I know this is not a known bug nor expected behaviour I started debugging.
I made a mockup and processed that against Antenna House and FOP,
the result of the test pages is correct and as expected.
So there needs to be something in the rest of the code that generates
the likely default first empty page
I have followed Kens suggestion of the auto-odd in the first-page
In my test setup the result is the same
I still have to wait for process results of that test in the live system
So it is down to debugging the system
Thanks for all your confirmations
Geert
At 02:19 16/12/2011, you wrote:
At 2011-12-16 01:35 +0100, Geert Bormans wrote:
I have parts in my document
each part generates 2 page-sequences
- one for the toc of the part (always 1 page, one left blank after that)
- one for the actual part content
Now I want each toc to start on an odd page (I force the pagenumber
to be 1for each)
And I want the part to start on page three
settings for the page sequence of the toc
force-page-count = even
initial-page-number = 1
settings for the page sequence of the part content
force-page-count = even
Rather than that, I typically use: initial-page-number="auto-odd"
But it should produce the same result. If you do use that then you
don't need the force-page-count="even" on the first sequence.
All is fine when the page count odd for the part content (I get one
blank page at the end as expected)
If the page count is even, I get two blank pages.
That sounds like a bug. There should never be two blank pages
generated at the end of a page sequence based on the length of the
page sequence. Which processor are you using?
I would like to see no empty pages
No kidding!
Is this expected behaviour?
Nope.
(and what to do to prevent this?)
Use another processor?
Would it be a marker issue? I have markers in the FO for use with
the headers/footers
Would markers naturaly float to the next page?
Markers are only supposed to show up on pages triggered by content
or by page count, without any concept of "floating" to the next page.
I hope this helps, Geert (though I recognize it doesn't explain what
is wrong in your environment).
. . . . . . . . . . Ken
--
Contact us for world-wide XML consulting and instructor-led training
Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h
Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/
G. Ken Holman mailto:gkholman(_at_)CraneSoftwrights(_dot_)com
Google+ profile: https://plus.google.com/116832879756988317389/about
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>
--~--
--~------------------------------------------------------------------
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>
--~--