When the column-count is greater than the default 1 column, very long tables (multiple pages) that have span="all" block around it stop spanning after the first page and revert back to column mode. The table flows in the orginal column count and the width is is still span="all" width. Major overlapping text. <fo:region-body column-count="2" column-gap="1cm" .... ... <fo:flow flow-name="xsl-region-body"> ... <fo:block span="all"> <fo:table .... This was working but seems to of come up since the 0.91 release.
Created attachment 18198 [details] Big table spanning 2 columns Here is a XSL FO file that gives and example of what I mean.
Created attachment 18199 [details] Example FO using latest Trunk version
Bug fixed in Trunk: http://svn.apache.org/viewcvs?rev=404751&view=rev
reproduced on Apache FOP Version 0.95
This was originally attachment ID 24629 that was lost as part of the issues.apache.org data loss on 2009-11-26/27. Note that this attachment ID has since been re-used. The original attachment comment was: Bugfix for 0.95
(In reply to comment #5) > This was originally attachment ID 24629 that was lost as part of the > issues.apache.org data loss on 2009-11-26/27. > > Note that this attachment ID has since been re-used. > > The original attachment comment was: > Bugfix for 0.95 Thanks for your patch. The FO document attached to this bug report renders fine with the latest Trunk, so the issue has somehow been fixed meanwhile. If you can test the Trunk and have a document that doesn't render well with it, feel free to attach it to this bug report (and re-open that latter) and we are going to have a further look at it. Meanwhile, your patch may be useful to users who must stick with 0.95. Thanks, Vincent
Created attachment 24650 [details] Bugfix for 0.95 This is originally attachment ID 24629 that was lost as part of the issues.apache.org data loss on 2009-11-26/27. (In addition to comment #5)
This has come back in apache fop version 6.X
I can't reproduce the issue with the attached example. Can you provide a sample FO file illustrating the problem with the latest Trunk? Thanks, Vincent
vincent reports irreproducible in trunk; since no further information has been providing, i'm moving to resolved+worksforme
batch transition resolved+worksforme to closed+worksforme; if you believe this remains a bug and can demonstrate it with appropriate input FO file and output PDF file (as applicable), then you may reopen