Ah, so we need to define first, what we really want to expect. :-) Does
the spec say anything about the expected behaviour?
On 02.10.2005 00:57:07 J.Pietschmann wrote:
Jeremias Maerki wrote:
On 27.09.2005 16:38:23 Luca Furini wrote:
[the usual layout oscillation/convergence problem]
What is
On Oct 3, 2005, at 16:11, Jeremias Maerki wrote:
On 02.10.2005 00:57:07 J.Pietschmann wrote:
Jeremias Maerki wrote:
On 27.09.2005 16:38:23 Luca Furini wrote:
[the usual layout oscillation/convergence problem]
What is the expected output?
In this case it has to generate a blank page IMO.
On Oct 3, 2005, at 21:22, J.Pietschmann wrote:
Umm, emm, blank means no area at all on the page body, not even one
with bpd=0. E.g.
fo:flow ...
fo:block/
fo:block break-before=page/
/fo:flow
would create two non-blank pages. Or so I think.
I see and fully agree, but IIRC, one of the
Jeremias Maerki wrote:
On 27.09.2005 16:38:23 Luca Furini wrote:
[the usual layout oscillation/convergence problem]
What is the expected output?
In this case it has to generate a blank page IMO.
The expected output is that there is some content (area with bpd0) on
the last page, even if
Jeremias Maerki wrote:
What is the expected output?
In this case it has to generate a blank page IMO.
Oh, right, I did not think of an empty page! :-)
The problem is with the page x of y hack that won't work like this if
the last empty block ends up on the second-to-last page. [...]
What
Jeremias Maerki wrote:
It's an interesting idea. However, I suspect this will probably not be
necessary. We should be able to make the breaker clever enough to handle
this particular case.
When the page bpd depends on the page-masters, things becomes very
strange. Not only it's difficult to
On 27.09.2005 16:38:23 Luca Furini wrote:
Jeremias Maerki wrote:
It's an interesting idea. However, I suspect this will probably not be
necessary. We should be able to make the breaker clever enough to handle
this particular case.
When the page bpd depends on the page-masters,
It's an interesting idea. However, I suspect this will probably not be
necessary. We should be able to make the breaker clever enough to handle
this particular case. ATM, I don't have free brain capacity to dive into
this (even though this is an important and long-awaited feature) but it
may make
On Sep 26, 2005, at 16:03, Jeremias Maerki wrote:
It's an interesting idea. However, I suspect this will probably not be
necessary. We should be able to make the breaker clever enough to
handle
this particular case. ATM, I don't have free brain capacity to dive
into
this (even though this is
Hi,
(Apologies for the many posts... I'm definitely on a roll :-))
Now that it has been made clear to me that the layout-engine first
calculates *all* break-possibilities, IMO this also seems to make
implementing page-position=last much, much easier.
Assuming that no areas are generated
10 matches
Mail list logo
