[jira] [Commented] (FOP-2060) adjoining blocks with break-before=page break-after=page cause extra empty page
[ https://issues.apache.org/jira/browse/FOP-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14584022#comment-14584022 ] Matthias Reischenbacher commented on FOP-2060: -- It makes more sense to wait until the refactoring of the LayoutContext handling is done as part of FOP-2469, before continuing to look into this, right? adjoining blocks with break-before=page break-after=page cause extra empty page --- Key: FOP-2060 URL: https://issues.apache.org/jira/browse/FOP-2060 Project: FOP Issue Type: Bug Components: layout/unqualified Affects Versions: trunk Environment: Operating System: All Platform: All Reporter: Luis Bernardo Fix For: trunk Attachments: 2060-empty-block-issue.xml, test.fo, test.pdf This causes five pages instead of four: fo:block fo:blockpage 1/fo:block fo:block break-before=page break-after=pagepage 2/fo:block fo:block break-before=page break-after=pagepage 3/fo:block fo:blockpage 4/fo:block /fo:block The empty extra page happens between page 2 and page 3. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2462) Fop PDF Image Plugin broken since rev 1590626
[ https://issues.apache.org/jira/browse/FOP-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14584030#comment-14584030 ] Matthias Reischenbacher commented on FOP-2462: -- Simon: I'd like to investigate why our PDFs are generated differently. Could you please attach a PDF without compression? Thanks! Fop PDF Image Plugin broken since rev 1590626 - Key: FOP-2462 URL: https://issues.apache.org/jira/browse/FOP-2462 Project: FOP Issue Type: Bug Components: image/unqualified Affects Versions: trunk Reporter: Matthias Reischenbacher Attachments: fop-2462-acrobat-error-message.png, fop-2462-external-pdf.pdf, fop-2462-test-case-null-filter.pdf, fop-2462-test-case.pdf, fop-2462-test-case.xml, out.pdf Rendering the attached sample fo and pdf file with FOP and the PDF Image Plugin creates a corrupted PDF file since revision 1590626. The generated PDF file can be opened with Adobe Acrobat but when opening the page with the external PDF file an error message is displayed and no content is visible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2247) Vertical table border differs width, when horizontal border is omitted
[ https://issues.apache.org/jira/browse/FOP-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14584175#comment-14584175 ] Jan Tošovský commented on FOP-2247: --- I've just filled https://code.google.com/p/chromium/issues/detail?id=500023 and also sent similar wording to Adobe https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform (there is not a tracker available). Fortunately, in Firefox (pdf.js) borders are rendered correctly. I do not expect Adobe will change a default behaviour, but the signifficance of PDF viewer IMHO decreases nowadays in favor of native browser rendering. So please star this Chrome issue to move things forward :-) Just a small warning, Chrome's PDF plugin team is understaffed for long time. Vertical table border differs width, when horizontal border is omitted -- Key: FOP-2247 URL: https://issues.apache.org/jira/browse/FOP-2247 Project: FOP Issue Type: Bug Components: renderer/pdf Affects Versions: 1.1 Environment: Windows 7, JRE1.6 Reporter: Guest User Priority: Minor Following description applies to PDF view. When using a table grid to place contents on a page, the border width of the cell borders differ in their width. This happens when both, top and bottom border, are omitted. Here is an example, which nicely demonstrates the effect. See the comment in the code to know, which borders will be painted wrong: ?xml version=1.0? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=content page-width=210mm page-height=297mm margin=1cm fo:region-body/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=content fo:flow flow-name=xsl-region-body fo:table table-layout=auto fo:table-header fo:table-row fo:table-cell border=medium solid black border-bottom=nonefo:block white-space-treatment=preserve /fo:block/fo:table-cell fo:table-cell border=medium solid black border-bottom=nonefo:block white-space-treatment=preserve /fo:block/fo:table-cell fo:table-cell border=medium solid black border-bottom=nonefo:block white-space-treatment=preserve /fo:block/fo:table-cell /fo:table-row fo:table-row fo:table-cell border=medium solid black border-top=none border-bottom=nonefo:block white-space-treatment=preserve /fo:block/fo:table-cell !-- vertical borders of the following cell appear thicker then the rest: -- fo:table-cell border=medium solid black border-top=none border-bottom=nonefo:block white-space-treatment=preserve /fo:block/fo:table-cell fo:table-cell border=medium solid black border-top=none border-bottom=nonefo:block white-space-treatment=preserve /fo:block/fo:table-cell /fo:table-row fo:table-row fo:table-cell border=medium solid black border-top=nonefo:block white-space-treatment=preserve /fo:block/fo:table-cell fo:table-cell border=medium solid black border-top=nonefo:block white-space-treatment=preserve /fo:block/fo:table-cell fo:table-cell border=medium solid black border-top=nonefo:block white-space-treatment=preserve /fo:block/fo:table-cell /fo:table-row /fo:table-header fo:table-body fo:table-row fo:table-cellfo:block/fo:block/fo:table-cell fo:table-cellfo:block/fo:block/fo:table-cell fo:table-cellfo:block/fo:block/fo:table-cell /fo:table-row /fo:table-body /fo:table /fo:flow /fo:page-sequence /fo:root This can be seen on screen and on paper, as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2465) [PATCH] Links to 'last' page aren't working
[ https://issues.apache.org/jira/browse/FOP-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14584065#comment-14584065 ] Matthias Reischenbacher commented on FOP-2465: -- Fixed in http://svn.apache.org/viewvc?view=revisionrevision=1685165 -- My first commit, I hope I didn't do anything wrong. [PATCH] Links to 'last' page aren't working --- Key: FOP-2465 URL: https://issues.apache.org/jira/browse/FOP-2465 Project: FOP Issue Type: Bug Components: layout/page Reporter: Matthias Reischenbacher Attachments: fop-2465-link-to-last-page.patch, fop-2465-link-to-last-page.xml If there is a separate page master for the 'last' page and the layout is redone (see PageBreaker.redoLayout) links to content inside the last page don't work. My test case fo file contains a bookmark to a block on the last page. The following warning is displayed when generating PDF output: WARNING: 1 link target could not be fully resolved and now point to the top of the page or is dysfunctional. My Patch tries to fix the ID handling and replaces the old PageViewport instances inside the IDTracker with the one. Please let me know if there is a better way to fix this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FOP-2465) [PATCH] Links to 'last' page aren't working
[ https://issues.apache.org/jira/browse/FOP-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Reischenbacher resolved FOP-2465. -- Resolution: Fixed Fix Version/s: trunk [PATCH] Links to 'last' page aren't working --- Key: FOP-2465 URL: https://issues.apache.org/jira/browse/FOP-2465 Project: FOP Issue Type: Bug Components: layout/page Reporter: Matthias Reischenbacher Fix For: trunk Attachments: fop-2465-link-to-last-page.patch, fop-2465-link-to-last-page.xml If there is a separate page master for the 'last' page and the layout is redone (see PageBreaker.redoLayout) links to content inside the last page don't work. My test case fo file contains a bookmark to a block on the last page. The following warning is displayed when generating PDF output: WARNING: 1 link target could not be fully resolved and now point to the top of the page or is dysfunctional. My Patch tries to fix the ID handling and replaces the old PageViewport instances inside the IDTracker with the one. Please let me know if there is a better way to fix this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2477) Non uniform cell borders in complex table
[ https://issues.apache.org/jira/browse/FOP-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Tošovský updated FOP-2477: -- Attachment: table-border.pdf Adding PDF as well (to ease demonstration of this issue in various viewers). Non uniform cell borders in complex table - Key: FOP-2477 URL: https://issues.apache.org/jira/browse/FOP-2477 Project: FOP Issue Type: Bug Affects Versions: 1.1, trunk Reporter: Jan Tošovský Priority: Minor Attachments: table-border-expected.png, table-border.fo, table-border.pdf, table-border.png In complex tables with spanned cells the border is not rendered by the same thickness, which is apparent mainly when borders are anti-aliased if page is scaled down. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2486) Soft font support for TrueType fonts in PCL
[ https://issues.apache.org/jira/browse/FOP-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Meyer updated FOP-2486: -- Attachment: softfonts.pcl rasterized.pcl Attached two examples of before and after the changes. Soft font support for TrueType fonts in PCL --- Key: FOP-2486 URL: https://issues.apache.org/jira/browse/FOP-2486 Project: FOP Issue Type: Improvement Components: renderer/pcl Affects Versions: trunk Reporter: Robert Meyer Fix For: trunk Attachments: patch.diff, rasterized.pcl, softfonts.pcl Currently all fonts (except a limited set of native fonts) are rastered for PCL output. This has the problem of the documents being large in size and should FOP be used in the cloud, rendering to PCL would not be possible as it's using AWT. This patch in part resolves this problem by converting TrueType fonts to PCL soft fonts. This allows the size to be much smaller and has been a standard feature since PCL 5. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2486) [PATCH] Soft font support for TrueType fonts in PCL
[ https://issues.apache.org/jira/browse/FOP-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Meyer updated FOP-2486: -- Description: Currently all fonts (except a limited set of native fonts) are rastered for PCL output. This has the problem of the documents being large in size and should FOP be used in the cloud, rendering to PCL would not be possible as it's using AWT. This patch in part resolves this problem by converting TrueType fonts to PCL soft fonts. This allows the size to be much smaller and has been a standard feature since PCL 5. [EDIT] For all other fonts which are not TrueType it will still revert back to being rasterized. It will currently default to using soft fonts for TrueType fonts but this can overriden by using text-renderingbitmap/text-rendering. was: Currently all fonts (except a limited set of native fonts) are rastered for PCL output. This has the problem of the documents being large in size and should FOP be used in the cloud, rendering to PCL would not be possible as it's using AWT. This patch in part resolves this problem by converting TrueType fonts to PCL soft fonts. This allows the size to be much smaller and has been a standard feature since PCL 5. [PATCH] Soft font support for TrueType fonts in PCL --- Key: FOP-2486 URL: https://issues.apache.org/jira/browse/FOP-2486 Project: FOP Issue Type: Improvement Components: renderer/pcl Affects Versions: trunk Reporter: Robert Meyer Fix For: trunk Attachments: patch.diff, rasterized.pcl, softfonts.pcl Currently all fonts (except a limited set of native fonts) are rastered for PCL output. This has the problem of the documents being large in size and should FOP be used in the cloud, rendering to PCL would not be possible as it's using AWT. This patch in part resolves this problem by converting TrueType fonts to PCL soft fonts. This allows the size to be much smaller and has been a standard feature since PCL 5. [EDIT] For all other fonts which are not TrueType it will still revert back to being rasterized. It will currently default to using soft fonts for TrueType fonts but this can overriden by using text-renderingbitmap/text-rendering. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2182) org.apache.fop.render.rtf.RTFHandler.startPageSequence(RTFHandler.java:221)
[ https://issues.apache.org/jira/browse/FOP-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14583382#comment-14583382 ] simon steiner commented on FOP-2182: Fixed in FOP-2321 org.apache.fop.render.rtf.RTFHandler.startPageSequence(RTFHandler.java:221) --- Key: FOP-2182 URL: https://issues.apache.org/jira/browse/FOP-2182 Project: FOP Issue Type: Bug Reporter: Mathieu Malaterre Attachments: demo.fo I cannot build an rtf file from a fo. It keep on failing with: java.lang.NullPointerException at org.apache.fop.render.rtf.RTFHandler.startPageSequence(RTFHandler.java:221) at org.apache.fop.fo.pagination.PageSequence.startOfNode(PageSequence.java:119) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:325) at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:175) at org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1073) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:485) at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:300) at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:130) at org.apache.fop.cli.Main.startFOP(Main.java:177) at org.apache.fop.cli.Main.main(Main.java:208) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
