You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by bu...@apache.org on 2008/05/27 15:28:51 UTC
DO NOT REPLY [Bug 45079] New: multi page table with marker
https://issues.apache.org/bugzilla/show_bug.cgi?id=45079
Summary: multi page table with marker
Product: Fop
Version: 0.94
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: fo tree
AssignedTo: fop-dev@xmlgraphics.apache.org
ReportedBy: filippoweb@gmail.com
Created an attachment (id=22010)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=22010)
It's an invoice, basically composed by 3 tables, one for the header, one for
the footer and one for the body. if the document body is bigger than 2 pages
the error occurs
Using a marker to draw a table as a footnote, the marker retrieving code
returns a non-clean table object for the pages other than the first.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 45079] multi page table with marker
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45079
--- Comment #3 from Glenn Adams <gl...@skynav.com> 2012-04-07 01:44:53 UTC ---
resetting P2 open bugs to P3 pending further review
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 45079] multi page table with marker
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45079
Glenn Adams <gl...@skynav.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P2 |P3
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 45079] multi page table with marker
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45079
Glenn Adams <ga...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
--- Comment #4 from Glenn Adams <ga...@apache.org> 2012-04-11 06:16:32 UTC ---
change status from ASSIGNED to NEW for consistency
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 45079] multi page table with marker
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45079
--- Comment #2 from Andreas L. Delmelle <ad...@apache.org> 2008-06-01 04:36:07 PST ---
Created an attachment (id=22046)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=22046)
preliminary patch fixing the issue
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 45079] multi page table with marker
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45079
Andreas L. Delmelle <ad...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #1 from Andreas L. Delmelle <ad...@apache.org> 2008-06-01 04:28:43 PST ---
Additional info from the related thread on fop-dev@:
---
[Vincent: ]
When the document needs 3 pages, the table in the first marker (for the
footer area) must be laid out twice, on the first two pages. And there
seems to be a bug in the marker retrieving code that returns a non-clean
table object (I suspect the columns aren’t properly set). But after
a quick look I haven’t managed to track down the bug.
[Me: ]
At first glance, the problem seems to be the fact that the ColumnNumberManager
is not cloned with the table. This means that, the second time the table is
retrieved, it will use the same one as that for the first retrieval.
If I change that little detail (Table.clone()), the example renders to three
pages without an error in FOP Trunk.
However:
- enabling assertions does throw an error (could point to that one bug that has
been fixed in 0.95 head, but has not been merged back into the trunk yet).
- looking at the result, somehow I get two retrieved markers for the footer in
the second page...
---
In the meantime, I've also corrected the second issue locally. This was caused
by the TableBody.rowGroups member which was not reset in the clone.
This leaves only the AssertionError.
BTW: for FOP 0.95 (or later) you probably want to remove keep-together="always"
from the table-rows in the header/footer. The content cannot be broken over
multiple pages anyway, and using the keep-together also forces
keep-together.within-line="always" for the content of the table-cells.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.