Hi Vincent, 

> This is very probably another manifestation of bug #46322:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=46322
> See discussion here:
> http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/200812.mbox/<[email protected]>

I remember. But back then I thought, that would only be a problem with one 
line. 

> The bug is triggered even if the previous blocks also
> span the whole page. The fact that you didn't explicitly 
> specify span="all" on the previous block makes the code 
> believe that there is a change in the spanning, which 
> triggers some special (and buggy) page break handling.
> You found the workaround already. Hopefully it doesn't 
> upset your whole tool chain. That's all I can say for now :-\

No, I have not yet found the workaround. Only in the stripped example there's 
one column. Actually I get the problem in my two-column layout and there I 
can't remove the span="all". 

Can you think of a different workaround?
Can you guess when your new pagebreaking mechanism will be finished? 
Do you have a hint where I can find this special (and buggy) page break 
handling?

Regards,
 
Georg Datterl
 
------ Kontakt ------
 
Georg Datterl
 
Geneon media solutions gmbh
Gutenstetter Straße 8a
90449 Nürnberg
 
HRB Nürnberg: 17193
Geschäftsführer: Yong-Harry Steiert 

Tel.: 0911/36 78 88 - 26
Fax: 0911/36 78 88 - 20
 
www.geneon.de
 
Weitere Mitglieder der Willmy MediaGroup:
 
IRS Integrated Realization Services GmbH:    www.irs-nbg.de 
Willmy PrintMedia GmbH:                            www.willmy.de
Willmy Consult & Content GmbH:                 www.willmycc.de 
-----Ursprüngliche Nachricht-----
Von: Vincent Hennebert [mailto:[email protected]] 
Gesendet: Montag, 23. Februar 2009 12:39
An: [email protected]
Betreff: Re: span is influencing page breaking?

Hi Georg,

Georg Datterl wrote:
> Hi everybody, especially Vincent.
> 
> Attached fo-file contains a red block which is printed on the first page, 
> although there's not enough space left. If I remove the span="all" for the 
> block, it is printed on the next page. Can you tell me why span="all" is 
> influencing the page break here?

This is very probably another manifestation of bug #46322:
https://issues.apache.org/bugzilla/show_bug.cgi?id=46322

See discussion here:
http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/200812.mbox/<[email protected]>

The bug is triggered even if the previous blocks also span the whole page. The 
fact that you didn't explicitly specify span="all" on the previous block makes 
the code believe that there is a change in the spanning, which triggers some 
special (and buggy) page break handling.

You found the workaround already. Hopefully it doesn't upset your whole tool 
chain. That's all I can say for now :-\


Vincent

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


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

Reply via email to