Hi Pascal

Sorry if I'm not clear enough, I'll try to explain using an example:

Let's say that I have four events that I want to show. Every event represents 
one table row and must normally (!) be atomic.

Thus, from this situation

+---------+---------------------+  <-- Page start
|         |                     |
+---------+---------------------+
+---------+---------------------+
|         |                     |
|         |                     |
+---------+---------------------+
+---------+---------------------+
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
+---------+---------------------+
+---------+---------------------+
|         |                     |
|         |                     |
|         |                     |  <-- Normal page end
|         |                     |
|         |                     |
|         |                     |
+---------+---------------------+


I want this result:
+---------+---------------------+  <-- Page start
|         |                     |
+---------+---------------------+
+---------+---------------------+
|         |                     |
|         |                     |
+---------+---------------------+
+---------+---------------------+
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
+---------+---------------------+  <-- Page end
+---------+---------------------+  <-- Page start
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
+---------+---------------------+







                                   <-- Page end


As required, the table row containing one event is not split.

However, if one table row is bigger than the page
+---------+---------------------+  <-- Page start
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |  <-- Normal page end
|         |                     |
|         |                     |
|         |                     |
+---------+---------------------+

then FOP should split it, only because it can't possibly fit it on one page. 
But this should be the exception.
+---------+---------------------+  <-- Page start
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |
|         |                     |  <-- Page end
|         |                     |  <-- Page start
|         |                     |
|         |                     |
+---------+---------------------+







                                   <-- Page end

Is this clearer?


Best regards,
Eric

-----Ursprüngliche Nachricht-----
Von: Pascal Sancho [mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 6. Juni 2007 14:45
An: fop-users@xmlgraphics.apache.org
Betreff: RE: Overflow works in a strange way

> -----Message d'origine-----
> De : Lewis, Eric [mailto:[EMAIL PROTECTED] 
> Envoyé : mercredi 6 juin 2007 14:32
> 
> Hi Pascal
> 
> If I understand you right, you suggest something like
>         <fo:table-row keep-together="always" orphans="5">

Yes, but you should remove the keep-together property here

> I just tried it, but it doesn't solve the problem.
> 
> The whole event is put into one table row, and the event data 
> contains pseudo-HTML (like <br> and <p>) which is translated 
> into FO blocks and carriage returns.
> 
> So, showing one table row, it goes from
> 
> +---------+---------------------+
> |         |                     |
> +---------+---------------------+
> 
> (for normal event data) to
> 
> +---------+---------------------+
> |         |                     |
> |         |                     |
> |         |                     |
> |         |                     |
> |         |                     |
> |         |                     |
> |         |                     |
> |         |                     |
> |         |                     |
> |         |                     |
> |         |                     |
> |         |                     |
> +---------+---------------------+ 
> 
> (for my problem)
> 
> But it's all still *one* table row.

Hmm, I don't understand what you say here.
If you want to split a unique row in multiple rows, you should have look in 
your XSLT.
If you want that short rows are not cutted at the end of page, then use orphans 
property.
If you want that long rows don't overflow the body, then remove the 
keep-together property.

> Best regards,
> Eric

HTH,
Pascal

---------------------------------------------------------------------
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