Hi Pascal
Thanks for your help! I built in the following:
<fo:table-row>
<xsl:choose>
<xsl:when test="text and string-length(text) > 1800">
<xsl:attribute name="keep-together">auto</xsl:attribute>
</xsl:when>
<xsl:otherwise>
<xsl:attribute name="keep-together">always</xsl:attribute>
</xsl:otherwise>
</xsl:choose>
and this works perfectly.
However, I still don't know whether it's a FOP bug that before, the text went
down to the bottom of the page, ignoring margins and was partially lost.
Best regards,
Eric
-----Ursprüngliche Nachricht-----
Von: Pascal Sancho [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 6. Juni 2007 15:45
An: [email protected]
Betreff: RE: Overflow works in a strange way
> -----Message d'origine-----
> De : Lewis, Eric [mailto:[EMAIL PROTECTED]
> Envoyé : mercredi 6 juin 2007 15:33
>
> Hi Pascal
>
> Thanks! Now the only question I have is: How do I do it? ;-)
> I mean, how can decide beforehand when I need to change the
> 'orphans' and 'keep-together'? If there was some way that FOP
> would tell me "Watch out, you're going to have an overflow",
> then I could switch to the table rows without
> 'keep-together', but how can that happen?
In a perfect world, you should have the same set of properties on each fo:row
(with orphans, and without keep-together).
In the real world, you may have to tweek this...
A possible approach is to get the characters number in a cell,
Then choose what properties should be set or not, regarding this number...
> Or perhaps I'm just thinking in a non-FOP way?
FOP is OK for that
But XSLT size can grow and grow...
> Best regards,
> Eric
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]
