Hi, Keiron

I interpret 6.11.4 as follows. Number one, the names have to match -
"marker-class-name" and "retrieve-class-name". This is straightforward. It
defines qualifying areas.

Number two, qualifying areas are excluded if they follow the page being
formatted, regardless of "retrieve-boundary". So "retrieve-boundary"
essentially defines the backward limits. Finally, "retrieve-boundary" also
restricts qualifying areas in the backward direction: "page" says that if
it's not on the currently being-formatted page, it isn't up for

For "last-starting-within-page", "is-first" is clear enough I think. An FO
is generating and returning areas on the containing page, and the first one
is...well, the first one. :-) So it is the optimal candidate if its parent
FO has qualifying markers. With reference to your [2], return to the def'n
of "qualifying area": name-matching, period. I assume "last" in this context
means last geometrically, as opposed to some other "last". Eg, immediately
preceding as one normally reads a document.

I think whoever wrote this portion (markers) made the spec too abstruse. I
finally just broke my rule of adhering to the law, and considered the use
cases, and decided what made sense. :-)


> -----Original Message-----
> From: Keiron Liddle [mailto:[EMAIL PROTECTED]
> Sent: February 23, 2003 6:49 PM
> Subject: Re: markers in redesign
> Hi all,
> Is it correct that it should look for markers on the current page
> and if page
> boundary is current page then stop there. If boundary is
> page-sequence then
> keep going backwards on each page until a marker is found or
> reaches the start
> of the page-sequence and similarly for the document boundary.
> I'm trying to work out exactly how the markers should work.
> For the first starting within page and last ending I am fine
> with. First including
> carry-over seems okay.
> Last starting within page is a bit confusing. A statement [1] in
> the spec suggests
> that it shouldn't really find the last starting in the page but
> rather find the closest
> node to the root in the area tree that is the last starting area.
> Another statement [2]
> seems confusing but maybe this is if it is searching previous pages.
> So if this was in a page then block "a" would be the last
> starting in the page.
> -----start------
> ...
> <block id="a">
>   <block id="b">
>   </block>
> -------pos1-------------
>   <block id="c">
>   </block>
> </block>
> --------end-----------
> But if there is a column break in pos1 the last starting in page
> will become
> block "c" as block "a" is not starting in that part of the area tree.
> If this is the case then there are two possible cases when
> starting an area: isfirst
> and other. When finishing an area there are: islast, (had)
> isfirst and both. This will
> supply enough information to add only the needed markers to the
> area tree. These
> markers can then be kept for later retrieval.
> [1] "Every area in the hierarchy is considered preferential to,
> or "better" than, any
> area below it in the hierarchy."
> [2] "If there is no such area, then the last qualifying area in
> the containing page is
> better than any other area."
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to