I have a table that is displayed at the end of a page.
The table is a bit tall, so it is separated into two parts: one
at the end of the current page, and the other at the beginning of the
Is there a way to prevent FOP from cutting a table into pieces?
I tried to include the table
The FopImageFactory class appears to cache all references to images from
within rendered fop documents. If you are running FOP in a server process,
(a) this might cause a memory problem and (b) if images change between
renderings (as they do in my case), I get the old copy of
I think, this is a good method to be made available.
If the system is used to print manuals involving a lot of diagrams, this
call would be very useful (if different types of manuals are printed in
But this will not solve the problem of one fo file having a number of
How about a FopImageFactory.setCacheImages(boolean flag) method? So you
could turn off caching entirely? That's really what my current application
would like - methinks.
peter m. murray
On 3/7/02 9:57 AM, S. Jayaraman [EMAIL PROTECTED] wrote:
I think, this is a good
You can use the property break-before=page. Then your table will
always appear on a new page.
But if your table is longer than a page height, it will be continued on
a new page automatically.
Try to reduce the properties such as font-size, row-height, padding to
place your table on one page.
page-height=28mm? Have never seen before ...
It seems like you'd like to use A4Landscape format (width=297mm). Then
the page-height is 210mm.Try to use cm instead of mm.
Von: Olivier Rossel [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 6. Marz 2002 16:55
I'm trying to use FOP on the end of a chain of XMLFilters (sounds like
cocoon? it's for creating a directory of about 500 pdf files...).
It looks like I have the right class -
and I've got it to work using the run() method, but the format and render
(Crossposted to both fop-dev and fop-user. fop-user subscribers, please
post follow-ups to fop-dev)
alex [EMAIL PROTECTED] wrote:
Can anyone capture any important questions and answers which I should put
into the FAQ?
Well questions are easy, answers somewhat less:
Here is my impression
Sam Prokop wrote:
you can use keep-with-next and previous within the table-row tag, this
works fine, as long as the table fits into one page.
In my example, it is much more tricky.
My table is inside a cell in a table-row.
SO if this row is too low in the page, and the inner table a bit big, then
The following code works using the 0.20.2 release.
The issue in the initial code comes from the fact that the from-parent
function does not work on a block parent.
fo:block-container height=135mm width=75mm
Hi FOP Users,
Has anyone come across the problem of Servlet getting called multiple
times by IE (ver 5.5)
I use the following to render PDF using an input source, however I see in
log that that IE calls my servlet 2 times!
I use the following code as in the example for embedding fop in
In the latest version of fop, 0.20.3, when I try to use Adobe Acrobat Reader
to touch up the pdf files, I get an error
Touch up could not parse this page
Is there anything I could be doing wrong to cause this?
This is a known issue. There seem to be several approaches, which may depend
on your particular situation. There's a full discusssion of this on the
fop-dev list under the subject 'FO - PDF works with Netscape, not with IE'
which has the code for my solution (you can find it in the archives if not
I think I mave have encountered a bug. The attached XSL:FO file renders
in what I think is an incorrect manner with FOP 0.20.3.
The column itself ends up being split across two pages. The row,
however, contains a column with number-rows-spanned. I thought that a
The weird thing is that it only happens when a table cell's text is
split into three or more lines. The first two end up on the first page
and the last n - 2 on the second. I've attached a second fo file that
exhibits what I believe is the correct behaviour (zipped this time).
Thanks so much, it works for me.
It definitely saves the extra time spent in reload of servlet.
However I used the cache-control directive for IE :-
response.setHeader(Cache-Control, max-age=10); // workaround so IE
I looked at setting the max-age. But our reports can take two seconds or 2
minutes, so I really couldn't figure out a good setting.
From: Sharan, Dharmendra [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 07, 2002 1:38 PM
To: '[EMAIL PROTECTED]'
Mail list logo