The thing that bugs me is, when there is no qualifying area in the "containing page" (Note to spec editors: try saying currently-formatted page), after filtering, then it becomes anarchy. It seems like user preferences based on "retrieve-position" lose all relevance. In other words, there is an elaborate set of definitions based on the current page, with a hierarchy defined by "retrieve-position", but as soon as one establishes that there is no such qualifying area on the current page, than it's just the first qualifying area one can find, moving back in the document.
Exactly. All definitions regarding retrieve-position exclusively refer to the "current page". There is not a single word on what should happen if there is no matching marker on the current page but several on the previous page which are eligible. FOP picks the last, but there is absolutely nothing in the spec which backs this, and I searched thoroughly last weekend. BTW for the page sequence retrieving scope there is a "current page sequence" casually mentioned but definition of the term is left to imagination, in contrast to the meticulous definition of "current page".
Additionally, some oddball examples for discussion and fun:
<fo:block> <fo:footnote><fo:inline/><fo:footnote-body><fo:block> <fo:marker marker-class-name="foo"/>stuff</fo:block> </fo:footnote-body></fo:footnote> </fo:block> <fo:block> <fo:marker marker-class-name="foo"/>stuff </fo:block>
Which one is the last?
Similarly for <fo:block-container position="absolute" top="10cm" left="0cm" width="5cm" height="5cm> <fo:marker marker-class-name="foo"/><fo:block>stuff<fo:block> </fo:block-container> <fo:block-container position="absolute" top="0cm" left="0cm" width="5cm" height="5cm> <fo:marker marker-class-name="foo"/><fo:block>stuff<fo:block> </fo:block-container>
J.Pietschmann
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
