Hi all
I'm trying to apply the orphans and widows formatting rules, but I think
I've got something wrong.
Here's one example:
xsl:template match=whatever
fo:block orphans=4 widows=4
fo:table table-layout=fixed width=100% padding-before=5mm
fo:table-column column-width=25% /
should have been preceeded
by another error message if the TIFF codec is missing. Are you sure
there are no other error messages?
[1] https://jai-imageio.dev.java.net/
[2] http://xmlgraphics.apache.org/fop/trunk/graphics.html
(more inline below...)
On 24.01.2008 08:50:28 Lewis, Eric wrote:
Hi
I'm
Stefan
Lewis, Eric schrieb:
Hi Jeremias
Sorry, I should have written... I'm using FOP 0.93.
And no, I don't see any other error messages. The messages before and after
come from our own classes.
However, I set the log level to DEBUG, and this is what I see:
DEBUG
(method: loadImage()).
On 24.01.2008 09:44:21 Lewis, Eric wrote:
Hi Jeremias
Sorry, I should have written... I'm using FOP 0.93.
And no, I don't see any other error messages. The messages before and after
come from our own classes.
However, I set the log level to DEBUG, and this is what
not available?
On 24.01.2008 14:03:37 Lewis, Eric wrote:
Ok... while debugging I noticed that this function was called four times (for
two images), which made me a bit suspicous.
It turns out that the PDF render class does a two-pass rendering, once to
build the FOP are tree (I don't really know about
there. Either src has the right URI or not but there can't
be any difference between the two calls inside FOP because of that. If
the two calls are different all the same the reason must be another. Did
you manage to make it work? And if yes, what did you change?
On 24.01.2008 15:36:49 Lewis, Eric wrote
Message d'origine
De: Lewis, Eric [mailto:[EMAIL PROTECTED]
Date: mer. 19/09/2007 16:33
Hi
I'm having again a problem of page breaks and keeping
things together (I
this yet.
As a workaround, you can approximatively evaluate the text length and
choose to keep or not...
Pascal
Message d'origine
De: Lewis, Eric [mailto:[EMAIL PROTECTED]
Date: jeu. 20/09/2007 08:11
Yes, but the problem there is: If I do that, the long body text will
cause
Hi
I'm having again a problem of page breaks and keeping things together (I
last wrote to this list in June 07).
I have a paragraph with a title and a body afterwards that must be kept
together if possible. As a fix to my last problem, I check whether the
title and body should be kept together
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
=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
@xmlgraphics.apache.org
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
?
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
-Ursprüngliche Nachricht-
Von: Pascal Sancho [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 6. Juni 2007 15: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
14 matches
Mail list logo
