[jira] [Commented] (FOP-2267) fo:table nested in fo:inline cause overflow at the end of page
[ https://issues.apache.org/jira/browse/FOP-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13693037#comment-13693037 ] Chris Bowditch commented on FOP-2267: - Hi Json, Please don't report further bugs here. If you are sure the second issue is a bug, then please open a new JIRA issue for it, making sure to provide a sample FO to replicate it. If you aren't sure its a bug, please post your sample FO to the mailing list fop-us...@xmlgraphics.apache.org. Thanks, Chris fo:table nested in fo:inline cause overflow at the end of page -- Key: FOP-2267 URL: https://issues.apache.org/jira/browse/FOP-2267 Project: Fop Issue Type: Bug Affects Versions: 0.95, 1.1 Environment: Windows 7 Reporter: Json Attachments: data-was-lots-at-the-end-of-a-page.fo, data-was-lots-at-the-end-of-a-page.png, test.fo, TestResult(error).png I'm using FOP 0.95. In case the number of row in my table is over 100 rows (multipages). The row at the end of page is lost occasionally ? Please help me ! (Please see 'TestResult(error).png') -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FOP-2110) fo:table-row cannot be a link target
[ https://issues.apache.org/jira/browse/FOP-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13693635#comment-13693635 ] Carlos Villegas commented on FOP-2110: -- In addition to failing on the table-row, the target position in case of table-cell is wrong. It seems to always go to the top of the page instead. The target y coordinate is incorrect. I attached a slightly modified version of the previous test case that show the issue better. You can see it in the intermediate format output. Tested with FOP 1.1. fo:table-row cannot be a link target Key: FOP-2110 URL: https://issues.apache.org/jira/browse/FOP-2110 Project: Fop Issue Type: Bug Components: pdf Affects Versions: trunk Environment: Operating System: Mac OS X 10.4 Platform: PC Reporter: Jarno Elovirta Attachments: table-row-link.fo, table-row-link.log When fo:table-row with an id attribute is used as a fo:basic-link destination, Unresolved ID reference ... error is thrown. Linking to fo:table-cell works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FOP-2110) fo:table-row cannot be a link target
[ https://issues.apache.org/jira/browse/FOP-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Villegas updated FOP-2110: - Attachment: table-row-link2.fo Extended text case to differentiate better between block and cell's position. fo:table-row cannot be a link target Key: FOP-2110 URL: https://issues.apache.org/jira/browse/FOP-2110 Project: Fop Issue Type: Bug Components: pdf Affects Versions: trunk Environment: Operating System: Mac OS X 10.4 Platform: PC Reporter: Jarno Elovirta Attachments: table-row-link2.fo, table-row-link.fo, table-row-link.log When fo:table-row with an id attribute is used as a fo:basic-link destination, Unresolved ID reference ... error is thrown. Linking to fo:table-cell works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Commented] (FOP-2110) fo:table-row cannot be a link target
Any updates on this issue. Any indication of how difficult it is to fix? Carlos On 6/26/13 1:55 PM, Carlos Villegas (JIRA) wrote: [ https://issues.apache.org/jira/browse/FOP-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13693635#comment-13693635 ] Carlos Villegas commented on FOP-2110: -- In addition to failing on the table-row, the target position in case of table-cell is wrong. It seems to always go to the top of the page instead. The target y coordinate is incorrect. I attached a slightly modified version of the previous test case that show the issue better. You can see it in the intermediate format output. Tested with FOP 1.1. fo:table-row cannot be a link target Key: FOP-2110 URL: https://issues.apache.org/jira/browse/FOP-2110 Project: Fop Issue Type: Bug Components: pdf Affects Versions: trunk Environment: Operating System: Mac OS X 10.4 Platform: PC Reporter: Jarno Elovirta Attachments: table-row-link.fo, table-row-link.log When fo:table-row with an id attribute is used as a fo:basic-link destination, Unresolved ID reference ... error is thrown. Linking to fo:table-cell works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FOP-2269) fo:marker for subtotals by page
Lisdiana Rodriguez Alvarado created FOP-2269: Summary: fo:marker for subtotals by page Key: FOP-2269 URL: https://issues.apache.org/jira/browse/FOP-2269 Project: Fop Issue Type: Bug Reporter: Lisdiana Rodriguez Alvarado Priority: Blocker Hi, I'm working in a project that must generate a PDF Invoice using a XML as source. I'm using FOP 1.1 and the PDFs are generated almost like I expect, but my current problem is that each page must show subtotals. I need these totals by page, not accumulative. I'm trying using fo:retrieve-marker (retrieve-boundary=page) in the page footer and also with fo:retrieve-table-marker(retrieve-boundary-within-table=page) in the footer of a table. However in both cases, subtotals contains not just the accumulative in the current page but the amounts in the previous ones. I've been looking samples but I can't find what I'm doing wrong. I need to know if it's possible to do what I need to, and if so, I need a sample or guide to know how to reset the subtotals in every page. Thanks in advance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
