Hi Pascal
If I understand you right, you suggest something like
<fo:table-row keep-together="always" orphans="5">
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.
Best regards,
Eric
-----Ursprüngliche Nachricht-----
Von: Pascal Sancho [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 6. Juni 2007 14:19
An: [email protected]
Betreff: RE: Overflow works in a strange way
Eric, you can use the property orphans on fo:table-rows, telling the minimum
number of line in your row at bottom of page.
HTH,
Pascal
> -----Message d'origine-----
> De : Lewis, Eric [mailto:[EMAIL PROTECTED]
> Envoyé : mercredi 6 juin 2007 14:02
> À : [email protected]
> Objet : AW: Overflow works in a strange way
>
> Hi Pascal
>
> The problem is that if I use keep-together="auto", then the
> events are ripped apart, like
>
>
> 20th September 2006 Clinton wins soccer match
> ---------------------------------------------------------- Page break
> bla bla bla bla
>
> I want the events to be atomic, but still overflow into the
> next page, if necessary.
>
> Best regards,
> Eric
>
> -----Ursprüngliche Nachricht-----
> Von: Pascal Sancho [mailto:[EMAIL PROTECTED]
> Gesendet: Mittwoch, 6. Juni 2007 14:00
>
> Hi Eric,
>
> keep-together="always" on fo:table-row is probably what
> causes the warnings.
>
> You can try to remove this property.
>
> Pascal
>
>
> > -----Message d'origine-----
> > De : Lewis, Eric [mailto:[EMAIL PROTECTED] Envoyé :
> mercredi 6 juin
> > 2007 13:39
> >
> > Hi
> > I'm not very experienced with FOP, so please be gentle ;-)
> The report
> > I'm generating uses a historical view of events.
> > Every event must be kept in an atomic block, otherwise the report
> > looks very messy.
> >
> > For instance:
> > 20th September 2006 Clinton wins soccer match
> > bla bla bla bla
> >
> > 22nd September 2006 Bush wins baseball match
> > xyz xyz xyz xyz xyz
> >
> > There must be no page break within such an event.
> >
> > To achieve this, I use
> >
> > ...
> > <xsl:template match="histData">
> > <fo:table table-layout="fixed" width="14.7cm">
> > <fo:table-column column-width="2.5cm" />
> > <fo:table-column column-width="12.2cm" />
> > <fo:table-body>
> >
> > <fo:table-row keep-together="always"> ...
> >
> > This works well when the event's data is short. However, I
> have events
> > which contain a lot of event data, and thus FOP tells me
> WARN Content
> > of the region-body on page 6 overflows the available area in
> > block-progression dimension.
> > (fo:page-sequence, no context info
> > available)
> > WARN Content of the region-body on page 4 overflows the
> available area
> > in block-progression dimension.
> > (fo:page-sequence, no context info
> > available)
> >
> > The resulting PDF shows the event data up to the last bit
> of the page
> > - margins are ignored completely. Also, there's no
> overflow, the data
> > just stops at the end of the page and is cut off.
> >
> > Am I doing something wrong or is this a FOP problem?
> >
> > Best regards,
> > Eric
---------------------------------------------------------------------
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]
