> This still leaves the question: Does a block with a
> break-before="page" or a break-after="page" span two pages,
> or will it always be the first/last area on the page its
> content is rendered on?
> Examples
>
>
>
>
> ...
>
>
> Does last-ending-within-page retr
J.Pietschmann wrote at 3 Mar 2003 21:58:55 +0100:
> This still leaves the question: Does a block with a
> break-before="page" or a break-after="page" span two pages,
> or will it always be the first/last area on the page its
> content is rendered on?
One page (assuming it fits within one page
Peter B. West wrote:
More heart-in-the-mouth stuff for me, as I have coded the pre- and
post-order iterators in Node according to another interpretation, and I
have just had a mad search to try to justify it.
From the DOM Level 2 Traversal and Range spec glossary:
document order
The term d
J.Pietschmann wrote:
Hello,
I reexamined the marker problematic again.
...
"When comparing two areas to determine which one is better, the
terms "first" and "last" refer to the pre-order traversal order
of the area tree."
...
The quote above shows another problem: I'm used to the term
"pre-order"
Hello,
I reexamined the marker problematic again.
There are a few issues not yet mentioned. First some odd wording:
"The properties of the fo:retrieve-marker impose a hierarchy of
preference on the areas of the area tree..."
Unfortunately, they don't define this hierarchy directly but
instead defi
Keiron Liddle wrote:
Hi all,
I think I am getting an idea of the markers with Peter's and others points but I don't
fully understand how it should work or be implemented.
Anyway I have committed the code of how it might roughly work and hopefully it
is correct for the containing page. It isn't
Hi all,
I think I am getting an idea of the markers with Peter's and others points but I don't
fully understand how it should work or be implemented.
Anyway I have committed the code of how it might roughly work and hopefully it
is correct for the containing page. It isn't that much code anyway
Keiron Liddle wrote:
But the marker subtree from the previous page is tranposed into the same
"containing page".
Where do you get that from, how is it transposed, I have not seen any information
about this?
I was thinking of
6.11.4 fo:retrieve-marker
Areas:
The fo:retrieve-marker does not direc
> But the marker subtree from the previous page is tranposed into the same
> "containing page".
Where do you get that from, how is it transposed, I have not seen any information
about this?
Considering all the retrieve positions refer to areas in the "containing page" then
these markers transpo
Keiron Liddle wrote:
Keiron Liddle wrote:
How do you jump from the first sentance to the second one. The "containing
page" refers to the page where the marker is first formatted not where the
retrieve-marker occurs.
A marker generates areas after being retrieved by a retrieve-marker.
The contain
> Keiron Liddle wrote:
> > How do you jump from the first sentance to the second one. The "containing
> > page" refers to the page where the marker is first formatted not where the
> > retrieve-marker occurs.
>
> A marker generates areas after being retrieved by a retrieve-marker.
> The containi
Keiron Liddle wrote:
How do you jump from the first sentance to the second one. The "containing
page" refers to the page where the marker is first formatted not where the
retrieve-marker occurs.
A marker generates areas after being retrieved by a retrieve-marker.
The containing page is the page w
> -Original Message-
> From: Keiron Liddle [mailto:[EMAIL PROTECTED]
> Sent: February 25, 2003 9:16 PM
> To: [EMAIL PROTECTED]
> Subject: Re: markers in redesign
>
>
> > Looking at it again, I disagree. The "containing page" is the page
> > cont
> Looking at it again, I disagree. The "containing page" is the page
> containing the first area generated or returned by the children of the
> retrieved fo:marker. That is, the page on which the fo:retrieve-marker
> occurs in the static-content. This will only vary if the retrieval
> forces
J.Pietschmann wrote:
Arved Sandstrom wrote:
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 a
Arved Sandstrom wrote:
Comments below.
-Original Message-
From: Keiron Liddle [mailto:[EMAIL PROTECTED]
Sent: February 24, 2003 10:59 PM
Exactly. All definitions regarding retrieve-position exclusively
refer to the "current page". There is not a single word on what should
happen if there
Comments below.
> -Original Message-
> From: Keiron Liddle [mailto:[EMAIL PROTECTED]
> Sent: February 24, 2003 10:59 PM
> To: [EMAIL PROTECTED]
> Subject: Re: markers in redesign
>
> > Exactly. All definitions regarding retrieve-position exclusively
> > refe
> I haven't looked at markers too closely, but I would tend to think that,
> in the first case, block c is the last-starting-within-page. Blocks a,
> b and c all qualify; they all have an is-first trait of "true". So
> which one follows all others in the area tree, *in pre-order traversal
> o
> 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 absolutel
> Keiron,
>
> I haven't looked at markers too closely, but I would tend to think that,
> in the first case, block c is the last-starting-within-page. Blocks a,
> b and c all qualify; they all have an is-first trait of "true". So
> which one follows all others in the area tree, *in pre-order t
Arved Sandstrom wrote:
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
Arved Sandstrom wrote:
I assume "last" in this context
means last geometrically, as opposed to some other "last".
I'd think it's the last area generated and inserted in the area
tree by the parent FO of the marker, if applicable. This is of
course usually the last, geometrically, for some reasonabl
Comments inline.
> -Original Message-
> From: Tony Graham [mailto:[EMAIL PROTECTED]
> Sent: February 24, 2003 10:26 AM
> To: [EMAIL PROTECTED]
> Subject: RE: markers in redesign
>
>
> Arved Sandstrom wrote at 24 Feb 2003 08:01:40 -0400:
> > Comments be
Arved Sandstrom wrote at 24 Feb 2003 08:01:40 -0400:
> Comments below.
>
> > -Original Message-
> > From: Peter B. West [mailto:[EMAIL PROTECTED]
> > Sent: February 24, 2003 6:53 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: markers in redesign
Arved Sandstrom wrote:
...
That means, to me, first, that we use the naming to identify qualifying
areas.
Two, we use "retrieve-boundary" to filter out qualifying areas. I make that
distinction, because qualifying areas are defined by the naming alone.
Three, we use "retrieve-position" coupled
Comments below.
> -Original Message-
> From: Peter B. West [mailto:[EMAIL PROTECTED]
> Sent: February 24, 2003 6:53 AM
> To: [EMAIL PROTECTED]
> Subject: Re: markers in redesign
>
[ SNIP ]
> It seems to me that the "hierarchy" is not the same as the area t
Keiron Liddle wrote:
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 similarl
te 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. :-)
Arved
> -Original Message-
> From: Keiron Liddle [mailto:[EMAIL PROTECTED]
> Sent: February 23, 2003 6:49 PM
>
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 bo
29 matches
Mail list logo
