update. I ending up messing around with my xml, so that I would have smaller page sequences.
On Tue, 14 Sep 2004 14:25:45 -0400, Jebus <[EMAIL PROTECTED]> wrote: > On Tue, 14 Sep 2004 19:19:22 +0200, J.Pietschmann <[EMAIL PROTECTED]> wrote: > > Jebus wrote: > > > Its all tables. Basically the pdf is a report with the table as a > > > grid. The one problem could be that I set a border for each table cell > > > so that I can have grid lines. > > > > Doesn't matter. > > > > Actually is did make a difference. Taking out the border for the each > table cell helped quite a bit. > > > > like to here. I looked for an equivalent to the html cellspacing but > > > didn't find one for xsl:fo. > > > > What does the equivalent to html cellspacing have to do with > > visible border lines? > > > > What I am trying to do is get white space between each table cell. I > was using a white border. If there is another way I would like to > know. > > > > Would it be better to add extra rows and > > > columns to make the grid lines work ? > > > > Makes things worse. Don't do this. Tables take a lot of memory because > > a) they consist of lots of FOs, each generating a Java object, and > > b) the FO Java objects keep references to Area Java objects generated > > during the layout process. > > Both of these object sets are released after a page sequence ends. > > All other FOs release their Area objects already after a page is > > rendered. > > > > You can try to get the latest code from the CVS maintenance branch > > (see FOP website for instructions), compile, and see whether it > > processes your FO without NPEs. If so, it should solve your problem. > > > > > I checkout the branch fop-0_20_5 that didn't seem to make a difference. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
