[jira] [Commented] (FOP-2511) Null pointer exception when transforming to PDF with FOP 2.0
[
https://issues.apache.org/jira/browse/FOP-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693061#comment-14693061
]
Thanasis Giannimaras commented on FOP-2511:
---
Have you tried using trunk? I think this issue is a duplicate of
https://issues.apache.org/jira/browse/FOP-2461 which was patched recently by
Andreas L. Delmelle on trunk.
Null pointer exception when transforming to PDF with FOP 2.0
Key: FOP-2511
URL: https://issues.apache.org/jira/browse/FOP-2511
Project: FOP
Issue Type: Bug
Affects Versions: 2.0
Environment: OS X 10.9.5 . Tested both with JDK 1.7.0_45 and JDK 1.6.0
Reporter: Johan Persson
Priority: Critical
Labels: fop, nullpointer
When trying to transform to PDF I'm experiencing a NULL pointer exception.
See below. The same fo-file used as source works without problem with FOP 1.1
The source for the fo-file is a set of DocBook 5 sources transformed using
XSLTproc. The fo-file that produces the crash can be found at my Google-Drive
at:
https://drive.google.com/folderview?id=0BypRwfn2A3s6fnN6NW1PU1BEd3JiTzdyYlg0NjZxRTNFbFhUM21UMmw1ZUNjRGlYb1c2T28usp=sharing
{{java.lang.NullPointerException
at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288)
at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115)
at org.apache.fop.cli.Main.startFOP(Main.java:186)
at org.apache.fop.cli.Main.main(Main.java:217)
Caused by: java.lang.NullPointerException
at
org.apache.fop.layoutmgr.list.ListItemLayoutManager.getCombinedKnuthElementsForListItem(ListItemLayoutManager.java:405)
at
org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:326)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:498)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:103)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
at
org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:223)
at
org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:147)
at
org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:116)
at
org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:69)
at
org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:252)
at
org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:643)
at
org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:178)
at
org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:158)
at
org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:384)
at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:112)
at
org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:138)
at
[jira] [Updated] (FOP-2491) FOP 2.0 cannot support open-type font
[ https://issues.apache.org/jira/browse/FOP-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2491: -- Attachment: fop.xconf otfSubset.patch test.fo before.pdf after.pdf FOP 2.0 cannot support open-type font - Key: FOP-2491 URL: https://issues.apache.org/jira/browse/FOP-2491 Project: FOP Issue Type: Bug Affects Versions: 2.0 Environment: FOP: 2.0 Open Font: Noto-Sans Cjk (https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip) Reporter: Leo Yang Attachments: after.pdf, before.pdf, fop.xconf, otfSubset.patch, test.fo Symptom: Based on FOP 2.0 release, the open-type font can be embedded into PDF document, however, based on the testing with FOP 2.0, the google-noto-sans-Cjk font cannot be embedded into PDF document. How to repeat: 1. Get FOP 2.0 library. 2. Get Google-Noto-Sans from https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip. 3. Set the fop.xconf as following: font embed-url=file:///C:/Font/NotoSans.otf embedding-mode=subset font-triplet name=Noto Sans CJK TC Regular style=normal weight=normal/ /font 4. Set the FOP as following: ?xml version=1.0 encoding=UTF-8? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master margin=2cm page-width=21.0cm page-height=29.7cm master-name=A4-portrait fo:region-body/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=A4-portrait fo:flow flow-name=xsl-region-body fo:block font-family=Noto Sans CJK TC RegularHello Noto-OTF!/fo:block /fo:flow /fo:page-sequence /fo:root 5. Generate the PDF, there is no error reported. 6. Open the PDF file in Acro-Reader, it will report the cannot extract the embedded font error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2510) Infinite Loop
[ https://issues.apache.org/jira/browse/FOP-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2510: -- Attachment: svnLoop.patch test.fo Infinite Loop - Key: FOP-2510 URL: https://issues.apache.org/jira/browse/FOP-2510 Project: FOP Issue Type: Bug Reporter: Thanasis Giannimaras Attachments: svnLoop.patch, test.fo If the flow-name in the fo:flow element maps to a region body belonging to a simple-page-master not referenced by the fo:page-sequence element , then fop enters an infinite loop. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2510) Infinite Loop
[ https://issues.apache.org/jira/browse/FOP-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2510: -- Description: If the flow-name in the fo:flow element maps to a region body belonging to a simple-page-master not referenced by the fo:page-sequence element , then fop enters an infinite loop. Submitted patch that throws a ValidationException when this happens. (was: If the flow-name in the fo:flow element maps to a region body belonging to a simple-page-master not referenced by the fo:page-sequence element , then fop enters an infinite loop. ) Infinite Loop - Key: FOP-2510 URL: https://issues.apache.org/jira/browse/FOP-2510 Project: FOP Issue Type: Bug Reporter: Thanasis Giannimaras Attachments: svnLoop.patch, test.fo If the flow-name in the fo:flow element maps to a region body belonging to a simple-page-master not referenced by the fo:page-sequence element , then fop enters an infinite loop. Submitted patch that throws a ValidationException when this happens. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2491) FOP 2.0 cannot support open-type font
[ https://issues.apache.org/jira/browse/FOP-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2491: -- Attachment: svnSubset.patch FOP 2.0 cannot support open-type font - Key: FOP-2491 URL: https://issues.apache.org/jira/browse/FOP-2491 Project: FOP Issue Type: Bug Affects Versions: 2.0 Environment: FOP: 2.0 Open Font: Noto-Sans Cjk (https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip) Reporter: Leo Yang Attachments: after.pdf, before.pdf, fop.xconf, svnSubset.patch, test.fo Symptom: Based on FOP 2.0 release, the open-type font can be embedded into PDF document, however, based on the testing with FOP 2.0, the google-noto-sans-Cjk font cannot be embedded into PDF document. How to repeat: 1. Get FOP 2.0 library. 2. Get Google-Noto-Sans from https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip. 3. Set the fop.xconf as following: font embed-url=file:///C:/Font/NotoSans.otf embedding-mode=subset font-triplet name=Noto Sans CJK TC Regular style=normal weight=normal/ /font 4. Set the FOP as following: ?xml version=1.0 encoding=UTF-8? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master margin=2cm page-width=21.0cm page-height=29.7cm master-name=A4-portrait fo:region-body/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=A4-portrait fo:flow flow-name=xsl-region-body fo:block font-family=Noto Sans CJK TC RegularHello Noto-OTF!/fo:block /fo:flow /fo:page-sequence /fo:root 5. Generate the PDF, there is no error reported. 6. Open the PDF file in Acro-Reader, it will report the cannot extract the embedded font error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2491) FOP 2.0 cannot support open-type font
[ https://issues.apache.org/jira/browse/FOP-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14681876#comment-14681876 ] Thanasis Giannimaras commented on FOP-2491: --- The issue was fixed by using the correct encoding values when updating the offsets for the private font dictionary FOP 2.0 cannot support open-type font - Key: FOP-2491 URL: https://issues.apache.org/jira/browse/FOP-2491 Project: FOP Issue Type: Bug Affects Versions: 2.0 Environment: FOP: 2.0 Open Font: Noto-Sans Cjk (https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip) Reporter: Leo Yang Attachments: after.pdf, before.pdf, fop.xconf, otfSubset.patch, test.fo Symptom: Based on FOP 2.0 release, the open-type font can be embedded into PDF document, however, based on the testing with FOP 2.0, the google-noto-sans-Cjk font cannot be embedded into PDF document. How to repeat: 1. Get FOP 2.0 library. 2. Get Google-Noto-Sans from https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip. 3. Set the fop.xconf as following: font embed-url=file:///C:/Font/NotoSans.otf embedding-mode=subset font-triplet name=Noto Sans CJK TC Regular style=normal weight=normal/ /font 4. Set the FOP as following: ?xml version=1.0 encoding=UTF-8? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master margin=2cm page-width=21.0cm page-height=29.7cm master-name=A4-portrait fo:region-body/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=A4-portrait fo:flow flow-name=xsl-region-body fo:block font-family=Noto Sans CJK TC RegularHello Noto-OTF!/fo:block /fo:flow /fo:page-sequence /fo:root 5. Generate the PDF, there is no error reported. 6. Open the PDF file in Acro-Reader, it will report the cannot extract the embedded font error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2491) FOP 2.0 cannot support open-type font
[ https://issues.apache.org/jira/browse/FOP-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2491: -- Attachment: (was: otfSubset.patch) FOP 2.0 cannot support open-type font - Key: FOP-2491 URL: https://issues.apache.org/jira/browse/FOP-2491 Project: FOP Issue Type: Bug Affects Versions: 2.0 Environment: FOP: 2.0 Open Font: Noto-Sans Cjk (https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip) Reporter: Leo Yang Attachments: after.pdf, before.pdf, fop.xconf, test.fo Symptom: Based on FOP 2.0 release, the open-type font can be embedded into PDF document, however, based on the testing with FOP 2.0, the google-noto-sans-Cjk font cannot be embedded into PDF document. How to repeat: 1. Get FOP 2.0 library. 2. Get Google-Noto-Sans from https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip. 3. Set the fop.xconf as following: font embed-url=file:///C:/Font/NotoSans.otf embedding-mode=subset font-triplet name=Noto Sans CJK TC Regular style=normal weight=normal/ /font 4. Set the FOP as following: ?xml version=1.0 encoding=UTF-8? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master margin=2cm page-width=21.0cm page-height=29.7cm master-name=A4-portrait fo:region-body/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=A4-portrait fo:flow flow-name=xsl-region-body fo:block font-family=Noto Sans CJK TC RegularHello Noto-OTF!/fo:block /fo:flow /fo:page-sequence /fo:root 5. Generate the PDF, there is no error reported. 6. Open the PDF file in Acro-Reader, it will report the cannot extract the embedded font error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FOP-2510) Infinite Loop
Thanasis Giannimaras created FOP-2510: - Summary: Infinite Loop Key: FOP-2510 URL: https://issues.apache.org/jira/browse/FOP-2510 Project: FOP Issue Type: Bug Reporter: Thanasis Giannimaras Attachments: svnLoop.patch, test.fo If the flow-name in the fo:flow element maps to a region body belonging to a simple-page-master not referenced by the fo:page-sequence element , then fop enters an infinite loop. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2492) FOP-2.0 error when processing PDF with SVG image
[ https://issues.apache.org/jira/browse/FOP-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14644125#comment-14644125 ] Thanasis Giannimaras commented on FOP-2492: --- I think you should remove the use of font metrics in the fop.xconf file. FOP-2.0 error when processing PDF with SVG image Key: FOP-2492 URL: https://issues.apache.org/jira/browse/FOP-2492 Project: FOP Issue Type: New Feature Components: image/svg Affects Versions: 2.0 Environment: Linux Gentoo x86 Reporter: Aleksei Badyaev Priority: Blocker Attachments: fop.xconf, object-model.svg, test.fo, test.xml I try process my small FO document with SVG image to PDF, and i got following output: noformat июн 29, 2015 12:02:46 AM org.apache.fop.apps.FopConfParser configure INFO: Default page-height set to: 297mm июн 29, 2015 12:02:47 AM org.apache.fop.apps.FopConfParser configure INFO: Default page-width set to: 210mm июн 29, 2015 12:02:55 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Font Symbol,normal,700 not found. Substituting with Symbol,normal,400. июн 29, 2015 12:02:58 AM org.apache.fop.events.LoggingEventListener processEvent SEVERE: SVG graphic could not be rendered. Reason: java.lang.NullPointerException java.lang.NullPointerException at org.apache.fop.fonts.MultiByteFont.getBoundingBox(MultiByteFont.java:210) at org.apache.fop.fonts.LazyFont.getBoundingBox(LazyFont.java:301) at org.apache.fop.svg.font.FOPGVTGlyphVector.buildBoundingBoxes(FOPGVTGlyphVector.java:428) at org.apache.fop.svg.font.FOPGVTGlyphVector.getBoundingBoxes(FOPGVTGlyphVector.java:420) at org.apache.fop.svg.font.FOPGVTGlyphVector.getGlyphMetrics(FOPGVTGlyphVector.java:290) at org.apache.batik.bridge.GlyphLayout.doExplicitGlyphLayout(Unknown Source) at org.apache.batik.bridge.GlyphLayout.adjustTextSpacing(Unknown Source) at org.apache.batik.bridge.GlyphLayout.getAdvance2D(Unknown Source) at org.apache.batik.bridge.StrokingTextPainter.getTextChunk(Unknown Source) at org.apache.batik.bridge.StrokingTextPainter.computeTextRuns(Unknown Source) at org.apache.fop.svg.NativeTextPainter.computeTextRuns(NativeTextPainter.java:223) at org.apache.batik.bridge.StrokingTextPainter.getTextRuns(Unknown Source) at org.apache.batik.bridge.StrokingTextPainter.getBounds2D(Unknown Source) at org.apache.batik.bridge.TextNode.getPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getTransformedPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getTransformedPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getTransformedPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.paint(Unknown Source) at org.apache.fop.render.pdf.PDFImageHandlerSVG.handleImage(PDFImageHandlerSVG.java:207) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImage(AbstractIFPainter.java:249) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImage(AbstractIFPainter.java:205) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImageUsingImageHandler(AbstractIFPainter.java:170) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImageUsingURI(AbstractIFPainter.java:292) at org.apache.fop.render.pdf.PDFPainter.drawImage(PDFPainter.java:173) at org.apache.fop.render.intermediate.IFRenderer.drawImage(IFRenderer.java:1295) at org.apache.fop.render.intermediate.IFRenderer.renderImage(IFRenderer.java:1282) at org.apache.fop.render.AbstractRenderer.renderInlineViewport(AbstractRenderer.java:858) at org.apache.fop.render.AbstractPathOrientedRenderer.renderInlineViewport(AbstractPathOrientedRenderer.java:832) at org.apache.fop.render.intermediate.IFRenderer.renderInlineViewport(IFRenderer.java:863) at org.apache.fop.render.AbstractRenderer.renderInlineArea(AbstractRenderer.java:715) at
[jira] [Updated] (FOP-1777) Support for Font Kerning is Broken
[ https://issues.apache.org/jira/browse/FOP-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-1777: -- Attachment: kerningTrunk.pdf kerningTrunk.patch fop.xconf bchr.README bchr.pfb bchr.afm Support for Font Kerning is Broken -- Key: FOP-1777 URL: https://issues.apache.org/jira/browse/FOP-1777 Project: FOP Issue Type: Bug Components: font/unqualified Affects Versions: trunk Environment: Operating System: All Platform: All Reporter: Vincent Hennebert Attachments: bchr.README, bchr.afm, bchr.pfb, fop.xconf, kerning.fo, kerning.pdf, kerningTrunk.patch, kerningTrunk.pdf, screenshot-openoffice-writer.png The method o.a.f.fonts.Font.getKernValue expects two Unicode code points and returns the amount of kerning between the two corresponding glyphs. However, the implementation for Type 1 fonts interprets the two integers as character codes in the font's internal encoding (see o.a.f.fonts.type1.AFMFile.java). Those usually have nothing to do with Unicode code points. Moreover, trying to get kerning between two characters is inherently wrong: kerning applies to glyphs and not characters. A font may have several glyph variants for a same character, and kerning is likely to be different for each variant. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-1777) Support for Font Kerning is Broken
[ https://issues.apache.org/jira/browse/FOP-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640553#comment-14640553 ] Thanasis Giannimaras commented on FOP-1777: --- Fix for handling kerning for unencoded characters. Patch based on work provided by Luis Bernado with few changes. For mitigating potential performance issues, kerning has been disabled by deault (default option was true). As i could not include Nimbus Sans L font in fop, due to its license, for junit testing i used Bitstream Charter Regular (http://www.math.utah.edu/~beebe/fonts/charter-1.0.zip) which come with a more open, less restrictive license. Support for Font Kerning is Broken -- Key: FOP-1777 URL: https://issues.apache.org/jira/browse/FOP-1777 Project: FOP Issue Type: Bug Components: font/unqualified Affects Versions: trunk Environment: Operating System: All Platform: All Reporter: Vincent Hennebert Attachments: bchr.README, bchr.afm, bchr.pfb, fop.xconf, kerning.fo, kerning.pdf, kerningTrunk.patch, kerningTrunk.pdf, screenshot-openoffice-writer.png The method o.a.f.fonts.Font.getKernValue expects two Unicode code points and returns the amount of kerning between the two corresponding glyphs. However, the implementation for Type 1 fonts interprets the two integers as character codes in the font's internal encoding (see o.a.f.fonts.type1.AFMFile.java). Those usually have nothing to do with Unicode code points. Moreover, trying to get kerning between two characters is inherently wrong: kerning applies to glyphs and not characters. A font may have several glyph variants for a same character, and kerning is likely to be different for each variant. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2492) FOP-2.0 error when processing PDF with SVG image
[ https://issues.apache.org/jira/browse/FOP-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14627839#comment-14627839 ] Thanasis Giannimaras commented on FOP-2492: --- Can you please provide your xconf file? I tried both on windows and ubuntu and i can not reproduce the NPE exception (for both 2.0 and trunk). For both the environments I tried the svg seems to render fine. FOP-2.0 error when processing PDF with SVG image Key: FOP-2492 URL: https://issues.apache.org/jira/browse/FOP-2492 Project: FOP Issue Type: New Feature Components: image/svg Affects Versions: 2.0 Environment: Linux Gentoo x86 Reporter: Aleksei Badyaev Priority: Blocker Attachments: object-model.svg, test.fo, test.xml I try process my small FO document with SVG image to PDF, and i got following output: noformat июн 29, 2015 12:02:46 AM org.apache.fop.apps.FopConfParser configure INFO: Default page-height set to: 297mm июн 29, 2015 12:02:47 AM org.apache.fop.apps.FopConfParser configure INFO: Default page-width set to: 210mm июн 29, 2015 12:02:55 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Font Symbol,normal,700 not found. Substituting with Symbol,normal,400. июн 29, 2015 12:02:58 AM org.apache.fop.events.LoggingEventListener processEvent SEVERE: SVG graphic could not be rendered. Reason: java.lang.NullPointerException java.lang.NullPointerException at org.apache.fop.fonts.MultiByteFont.getBoundingBox(MultiByteFont.java:210) at org.apache.fop.fonts.LazyFont.getBoundingBox(LazyFont.java:301) at org.apache.fop.svg.font.FOPGVTGlyphVector.buildBoundingBoxes(FOPGVTGlyphVector.java:428) at org.apache.fop.svg.font.FOPGVTGlyphVector.getBoundingBoxes(FOPGVTGlyphVector.java:420) at org.apache.fop.svg.font.FOPGVTGlyphVector.getGlyphMetrics(FOPGVTGlyphVector.java:290) at org.apache.batik.bridge.GlyphLayout.doExplicitGlyphLayout(Unknown Source) at org.apache.batik.bridge.GlyphLayout.adjustTextSpacing(Unknown Source) at org.apache.batik.bridge.GlyphLayout.getAdvance2D(Unknown Source) at org.apache.batik.bridge.StrokingTextPainter.getTextChunk(Unknown Source) at org.apache.batik.bridge.StrokingTextPainter.computeTextRuns(Unknown Source) at org.apache.fop.svg.NativeTextPainter.computeTextRuns(NativeTextPainter.java:223) at org.apache.batik.bridge.StrokingTextPainter.getTextRuns(Unknown Source) at org.apache.batik.bridge.StrokingTextPainter.getBounds2D(Unknown Source) at org.apache.batik.bridge.TextNode.getPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getTransformedPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getTransformedPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getTransformedPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.paint(Unknown Source) at org.apache.fop.render.pdf.PDFImageHandlerSVG.handleImage(PDFImageHandlerSVG.java:207) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImage(AbstractIFPainter.java:249) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImage(AbstractIFPainter.java:205) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImageUsingImageHandler(AbstractIFPainter.java:170) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImageUsingURI(AbstractIFPainter.java:292) at org.apache.fop.render.pdf.PDFPainter.drawImage(PDFPainter.java:173) at org.apache.fop.render.intermediate.IFRenderer.drawImage(IFRenderer.java:1295) at org.apache.fop.render.intermediate.IFRenderer.renderImage(IFRenderer.java:1282) at org.apache.fop.render.AbstractRenderer.renderInlineViewport(AbstractRenderer.java:858) at org.apache.fop.render.AbstractPathOrientedRenderer.renderInlineViewport(AbstractPathOrientedRenderer.java:832) at org.apache.fop.render.intermediate.IFRenderer.renderInlineViewport(IFRenderer.java:863) at
[jira] [Comment Edited] (FOP-2492) FOP-2.0 error when processing PDF with SVG image
[ https://issues.apache.org/jira/browse/FOP-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14627839#comment-14627839 ] Thanasis Giannimaras edited comment on FOP-2492 at 7/15/15 10:09 AM: - Can you please provide your xconf file? I tried both on windows and ubuntu and i can not reproduce the NPE exception (for both 2.0 and trunk). For both the environments I tried the svg seems to render fine. I am getting several wanings about glyph not found in font though. was (Author: agiannimaras): Can you please provide your xconf file? I tried both on windows and ubuntu and i can not reproduce the NPE exception (for both 2.0 and trunk). For both the environments I tried the svg seems to render fine. FOP-2.0 error when processing PDF with SVG image Key: FOP-2492 URL: https://issues.apache.org/jira/browse/FOP-2492 Project: FOP Issue Type: New Feature Components: image/svg Affects Versions: 2.0 Environment: Linux Gentoo x86 Reporter: Aleksei Badyaev Priority: Blocker Attachments: object-model.svg, test.fo, test.xml I try process my small FO document with SVG image to PDF, and i got following output: noformat июн 29, 2015 12:02:46 AM org.apache.fop.apps.FopConfParser configure INFO: Default page-height set to: 297mm июн 29, 2015 12:02:47 AM org.apache.fop.apps.FopConfParser configure INFO: Default page-width set to: 210mm июн 29, 2015 12:02:55 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Font Symbol,normal,700 not found. Substituting with Symbol,normal,400. июн 29, 2015 12:02:58 AM org.apache.fop.events.LoggingEventListener processEvent SEVERE: SVG graphic could not be rendered. Reason: java.lang.NullPointerException java.lang.NullPointerException at org.apache.fop.fonts.MultiByteFont.getBoundingBox(MultiByteFont.java:210) at org.apache.fop.fonts.LazyFont.getBoundingBox(LazyFont.java:301) at org.apache.fop.svg.font.FOPGVTGlyphVector.buildBoundingBoxes(FOPGVTGlyphVector.java:428) at org.apache.fop.svg.font.FOPGVTGlyphVector.getBoundingBoxes(FOPGVTGlyphVector.java:420) at org.apache.fop.svg.font.FOPGVTGlyphVector.getGlyphMetrics(FOPGVTGlyphVector.java:290) at org.apache.batik.bridge.GlyphLayout.doExplicitGlyphLayout(Unknown Source) at org.apache.batik.bridge.GlyphLayout.adjustTextSpacing(Unknown Source) at org.apache.batik.bridge.GlyphLayout.getAdvance2D(Unknown Source) at org.apache.batik.bridge.StrokingTextPainter.getTextChunk(Unknown Source) at org.apache.batik.bridge.StrokingTextPainter.computeTextRuns(Unknown Source) at org.apache.fop.svg.NativeTextPainter.computeTextRuns(NativeTextPainter.java:223) at org.apache.batik.bridge.StrokingTextPainter.getTextRuns(Unknown Source) at org.apache.batik.bridge.StrokingTextPainter.getBounds2D(Unknown Source) at org.apache.batik.bridge.TextNode.getPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getTransformedPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getTransformedPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getTransformedPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.paint(Unknown Source) at org.apache.fop.render.pdf.PDFImageHandlerSVG.handleImage(PDFImageHandlerSVG.java:207) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImage(AbstractIFPainter.java:249) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImage(AbstractIFPainter.java:205) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImageUsingImageHandler(AbstractIFPainter.java:170) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImageUsingURI(AbstractIFPainter.java:292) at org.apache.fop.render.pdf.PDFPainter.drawImage(PDFPainter.java:173) at org.apache.fop.render.intermediate.IFRenderer.drawImage(IFRenderer.java:1295) at
[jira] [Comment Edited] (FOP-2492) FOP-2.0 error when processing PDF with SVG image
[ https://issues.apache.org/jira/browse/FOP-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14627839#comment-14627839 ] Thanasis Giannimaras edited comment on FOP-2492 at 7/15/15 10:09 AM: - Can you please provide your xconf file? I tried both on windows and ubuntu and i can not reproduce the NPE exception (for both 2.0 and trunk). For both the environments I tried the svg seems to render fine. I am getting several warnings about glyph not found in font though. was (Author: agiannimaras): Can you please provide your xconf file? I tried both on windows and ubuntu and i can not reproduce the NPE exception (for both 2.0 and trunk). For both the environments I tried the svg seems to render fine. I am getting several wanings about glyph not found in font though. FOP-2.0 error when processing PDF with SVG image Key: FOP-2492 URL: https://issues.apache.org/jira/browse/FOP-2492 Project: FOP Issue Type: New Feature Components: image/svg Affects Versions: 2.0 Environment: Linux Gentoo x86 Reporter: Aleksei Badyaev Priority: Blocker Attachments: object-model.svg, test.fo, test.xml I try process my small FO document with SVG image to PDF, and i got following output: noformat июн 29, 2015 12:02:46 AM org.apache.fop.apps.FopConfParser configure INFO: Default page-height set to: 297mm июн 29, 2015 12:02:47 AM org.apache.fop.apps.FopConfParser configure INFO: Default page-width set to: 210mm июн 29, 2015 12:02:55 AM org.apache.fop.events.LoggingEventListener processEvent WARNING: Font Symbol,normal,700 not found. Substituting with Symbol,normal,400. июн 29, 2015 12:02:58 AM org.apache.fop.events.LoggingEventListener processEvent SEVERE: SVG graphic could not be rendered. Reason: java.lang.NullPointerException java.lang.NullPointerException at org.apache.fop.fonts.MultiByteFont.getBoundingBox(MultiByteFont.java:210) at org.apache.fop.fonts.LazyFont.getBoundingBox(LazyFont.java:301) at org.apache.fop.svg.font.FOPGVTGlyphVector.buildBoundingBoxes(FOPGVTGlyphVector.java:428) at org.apache.fop.svg.font.FOPGVTGlyphVector.getBoundingBoxes(FOPGVTGlyphVector.java:420) at org.apache.fop.svg.font.FOPGVTGlyphVector.getGlyphMetrics(FOPGVTGlyphVector.java:290) at org.apache.batik.bridge.GlyphLayout.doExplicitGlyphLayout(Unknown Source) at org.apache.batik.bridge.GlyphLayout.adjustTextSpacing(Unknown Source) at org.apache.batik.bridge.GlyphLayout.getAdvance2D(Unknown Source) at org.apache.batik.bridge.StrokingTextPainter.getTextChunk(Unknown Source) at org.apache.batik.bridge.StrokingTextPainter.computeTextRuns(Unknown Source) at org.apache.fop.svg.NativeTextPainter.computeTextRuns(NativeTextPainter.java:223) at org.apache.batik.bridge.StrokingTextPainter.getTextRuns(Unknown Source) at org.apache.batik.bridge.StrokingTextPainter.getBounds2D(Unknown Source) at org.apache.batik.bridge.TextNode.getPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getTransformedPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getTransformedPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getTransformedPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown Source) at org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.getBounds(Unknown Source) at org.apache.batik.gvt.AbstractGraphicsNode.paint(Unknown Source) at org.apache.fop.render.pdf.PDFImageHandlerSVG.handleImage(PDFImageHandlerSVG.java:207) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImage(AbstractIFPainter.java:249) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImage(AbstractIFPainter.java:205) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImageUsingImageHandler(AbstractIFPainter.java:170) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImageUsingURI(AbstractIFPainter.java:292) at org.apache.fop.render.pdf.PDFPainter.drawImage(PDFPainter.java:173) at org.apache.fop.render.intermediate.IFRenderer.drawImage(IFRenderer.java:1295)
[jira] [Commented] (FOP-2500) Low performance of PCL printing
[ https://issues.apache.org/jira/browse/FOP-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14628172#comment-14628172 ] Thanasis Giannimaras commented on FOP-2500: --- Hello, can you provide the fo and xconf file in order to reproduce the issue? Thanks Low performance of PCL printing --- Key: FOP-2500 URL: https://issues.apache.org/jira/browse/FOP-2500 Project: FOP Issue Type: Bug Affects Versions: trunk Environment: N/A Reporter: Konrad Gajewski Priority: Critical Hi, Generating of the whole PCL page is taking too long. Check by the Java Visual VM shows that more time is consumed by following method: org.apache.fop.util.bitmap.DefaultMonochromeBitmapConverter.convertToMonochrome() 1200 ms -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FOP-2499) PDF/UA warnings for nested elements
Thanasis Giannimaras created FOP-2499: - Summary: PDF/UA warnings for nested elements Key: FOP-2499 URL: https://issues.apache.org/jira/browse/FOP-2499 Project: FOP Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras PDF with nested elements (and PDF/UA mode enabled) are giving out warnings when validated by http://www.access-for-all.ch/en/pdf-lab/pdf-accessibility-checker-pac.html (Inappropriate use of a type structure element warnings). This approach tries to solve the issue, by renaming the outermost structure element into a grouping element of type DIV. To notice the warning try to validate before pdf with accessibility checker mentioned above -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2499) PDF/UA warnings for nested elements
[ https://issues.apache.org/jira/browse/FOP-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2499: -- Attachment: test.fo pdfua.patch fop.xconf DejaVuLGCSerif.ttf before.pdf after.pdf PDF/UA warnings for nested elements --- Key: FOP-2499 URL: https://issues.apache.org/jira/browse/FOP-2499 Project: FOP Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Attachments: DejaVuLGCSerif.ttf, after.pdf, before.pdf, fop.xconf, pdfua.patch, test.fo PDF with nested elements (and PDF/UA mode enabled) are giving out warnings when validated by http://www.access-for-all.ch/en/pdf-lab/pdf-accessibility-checker-pac.html (Inappropriate use of a type structure element warnings). This approach tries to solve the issue, by renaming the outermost structure element into a grouping element of type DIV. To notice the warning try to validate before pdf with accessibility checker mentioned above -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2499) PDF/UA warnings for nested elements
[ https://issues.apache.org/jira/browse/FOP-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2499: -- Attachment: (was: DejaVuLGCSerif.ttf) PDF/UA warnings for nested elements --- Key: FOP-2499 URL: https://issues.apache.org/jira/browse/FOP-2499 Project: FOP Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Attachments: after.pdf, before.pdf, fop.xconf, pdfua.patch, test.fo PDF with nested elements (and PDF/UA mode enabled) are giving out warnings when validated by http://www.access-for-all.ch/en/pdf-lab/pdf-accessibility-checker-pac.html (Inappropriate use of a type structure element warnings). This approach tries to solve the issue, by renaming the outermost structure element into a grouping element of type DIV. To notice the warning try to validate before pdf with accessibility checker mentioned above -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2499) PDF/UA warnings for nested elements
[ https://issues.apache.org/jira/browse/FOP-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14626444#comment-14626444 ] Thanasis Giannimaras commented on FOP-2499: --- fonts used are the DejaVuLGCSerif.ttf, which are easily found at test/resources/fonts/ttf under fop directory. PDF/UA warnings for nested elements --- Key: FOP-2499 URL: https://issues.apache.org/jira/browse/FOP-2499 Project: FOP Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Attachments: after.pdf, before.pdf, fop.xconf, pdfua.patch, test.fo PDF with nested elements (and PDF/UA mode enabled) are giving out warnings when validated by http://www.access-for-all.ch/en/pdf-lab/pdf-accessibility-checker-pac.html (Inappropriate use of a type structure element warnings). This approach tries to solve the issue, by renaming the outermost structure element into a grouping element of type DIV. To notice the warning try to validate before pdf with accessibility checker mentioned above -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2491) FOP 2.0 cannot support open-type font
[ https://issues.apache.org/jira/browse/FOP-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14612099#comment-14612099 ] Thanasis Giannimaras commented on FOP-2491: --- Using embedding-mode=subset i am getting a blank page pdf. For embedding-mode=full the output is correct. You may want to use that option until the issue is fixed. FOP 2.0 cannot support open-type font - Key: FOP-2491 URL: https://issues.apache.org/jira/browse/FOP-2491 Project: FOP Issue Type: Bug Affects Versions: 2.0 Environment: FOP: 2.0 Open Font: Noto-Sans Cjk (https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip) Reporter: Leo Yang Symptom: Based on FOP 2.0 release, the open-type font can be embedded into PDF document, however, based on the testing with FOP 2.0, the google-noto-sans-Cjk font cannot be embedded into PDF document. How to repeat: 1. Get FOP 2.0 library. 2. Get Google-Noto-Sans from https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip. 3. Set the fop.xconf as following: font embed-url=file:///C:/Font/NotoSans.otf embedding-mode=subset font-triplet name=Noto Sans CJK TC Regular style=normal weight=normal/ /font 4. Set the FOP as following: ?xml version=1.0 encoding=UTF-8? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master margin=2cm page-width=21.0cm page-height=29.7cm master-name=A4-portrait fo:region-body/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=A4-portrait fo:flow flow-name=xsl-region-body fo:block font-family=Noto Sans CJK TC RegularHello Noto-OTF!/fo:block /fo:flow /fo:page-sequence /fo:root 5. Generate the PDF, there is no error reported. 6. Open the PDF file in Acro-Reader, it will report the cannot extract the embedded font error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FOP-2474) AFP Logical element tag incorrect character encoding
Thanasis Giannimaras created FOP-2474: - Summary: AFP Logical element tag incorrect character encoding Key: FOP-2474 URL: https://issues.apache.org/jira/browse/FOP-2474 Project: FOP Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras The dollar sign in the attribute value of the Tag Logical Element Structure, is not being displayed correctly (the cent sign is being showed instead). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2474) AFP Logical element tag incorrect character encoding
[ https://issues.apache.org/jira/browse/FOP-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2474: -- Attachment: tleEncoding.patch test.fo trunkFix.afp trunk.afp AFP Logical element tag incorrect character encoding Key: FOP-2474 URL: https://issues.apache.org/jira/browse/FOP-2474 Project: FOP Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Attachments: test.fo, tleEncoding.patch, trunk.afp, trunkFix.afp The dollar sign in the attribute value of the Tag Logical Element Structure, is not being displayed correctly (the cent sign is being showed instead). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2475) Tagged PDF footnote separator incorrect order
[ https://issues.apache.org/jira/browse/FOP-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2475: -- Attachment: fop.xconf footSep.patch test.fo before.pdf after.pdf Tagged PDF footnote separator incorrect order -- Key: FOP-2475 URL: https://issues.apache.org/jira/browse/FOP-2475 Project: FOP Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Attachments: after.pdf, before.pdf, footSep.patch, fop.xconf, test.fo For most cases footnote separator is being treated as an artifact so this is a non issue. But in cases where you have text working as footnote separator and not being labelled as an artifact, then the read out loud function (acrobat reader) reads it in the wrong order. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FOP-2475) Tagged PDF footnote separator incorrect order
Thanasis Giannimaras created FOP-2475: - Summary: Tagged PDF footnote separator incorrect order Key: FOP-2475 URL: https://issues.apache.org/jira/browse/FOP-2475 Project: FOP Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras For most cases footnote separator is being treated as an artifact so this is a non issue. But in cases where you have text working as footnote separator and not being labelled as an artifact, then the read out loud function (acrobat reader) reads it in the wrong order. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2475) [PATCH] Tagged PDF footnote separator incorrect order
[ https://issues.apache.org/jira/browse/FOP-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2475: -- Summary: [PATCH] Tagged PDF footnote separator incorrect order (was: Tagged PDF footnote separator incorrect order ) [PATCH] Tagged PDF footnote separator incorrect order -- Key: FOP-2475 URL: https://issues.apache.org/jira/browse/FOP-2475 Project: FOP Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Attachments: after.pdf, before.pdf, footSep.patch, fop.xconf, test.fo For most cases footnote separator is being treated as an artifact so this is a non issue. But in cases where you have text working as footnote separator and not being labelled as an artifact, then the read out loud function (acrobat reader) reads it in the wrong order. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2474) [PATCH]AFP Logical element tag incorrect character encoding
[ https://issues.apache.org/jira/browse/FOP-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2474: -- Summary: [PATCH]AFP Logical element tag incorrect character encoding (was: AFP Logical element tag incorrect character encoding) [PATCH]AFP Logical element tag incorrect character encoding --- Key: FOP-2474 URL: https://issues.apache.org/jira/browse/FOP-2474 Project: FOP Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Attachments: test.fo, tleEncoding.patch, trunk.afp, trunkFix.afp The dollar sign in the attribute value of the Tag Logical Element Structure, is not being displayed correctly (the cent sign is being showed instead). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2474) [PATCH] AFP Logical element tag incorrect character encoding
[ https://issues.apache.org/jira/browse/FOP-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2474: -- Summary: [PATCH] AFP Logical element tag incorrect character encoding (was: [PATCH]AFP Logical element tag incorrect character encoding) [PATCH] AFP Logical element tag incorrect character encoding Key: FOP-2474 URL: https://issues.apache.org/jira/browse/FOP-2474 Project: FOP Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Attachments: test.fo, tleEncoding.patch, trunk.afp, trunkFix.afp The dollar sign in the attribute value of the Tag Logical Element Structure, is not being displayed correctly (the cent sign is being showed instead). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2476) [PATCH] Tagged pdf: Tags are showing inthe wrong order in the acrobat's pro order panel
[ https://issues.apache.org/jira/browse/FOP-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2476: -- Summary: [PATCH] Tagged pdf: Tags are showing inthe wrong order in the acrobat's pro order panel (was: Tagged pdf: Tags are showing inthe wrong order in the acrobat's pro order panel) [PATCH] Tagged pdf: Tags are showing inthe wrong order in the acrobat's pro order panel --- Key: FOP-2476 URL: https://issues.apache.org/jira/browse/FOP-2476 Project: FOP Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Attachments: after.pdf, before.pdf, fop.xconf, svnregionorder.patch, test.fo If you open before.pdf using acrobat pro, you can see tha the order that the tags appear in the order panel ( view- navigational panel --order or Advanced --accessibility -- TouchUp reading order) is incorrect, which creates issues with 508 compliance (section 3.2 http://www.hhs.gov/web/508/accessiblefiles/checklistpdf.html) . That is happening because of the order that content appears in the pdf content stream! By changing the order that the regions are rendered in AbstractRenderer this can be easily fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2476) Tagged pdf: Tags are showing inthe wrong order in the acrobat's pro order panel
[ https://issues.apache.org/jira/browse/FOP-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2476: -- Attachment: fop.xconf svnregionorder.patch test.fo before.pdf after.pdf Tagged pdf: Tags are showing inthe wrong order in the acrobat's pro order panel --- Key: FOP-2476 URL: https://issues.apache.org/jira/browse/FOP-2476 Project: FOP Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Attachments: after.pdf, before.pdf, fop.xconf, svnregionorder.patch, test.fo If you open before.pdf using acrobat pro, you can see tha the order that the tags appear in the order panel ( view- navigational panel --order or Advanced --accessibility -- TouchUp reading order) is incorrect, which creates issues with 508 compliance (section 3.2 http://www.hhs.gov/web/508/accessiblefiles/checklistpdf.html) . That is happening because of the order that content appears in the pdf content stream! By changing the order that the regions are rendered in AbstractRenderer this can be easily fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2476) Tagged pdf: Tags are showing inthe wrong order in the acrobat's pro order panel
[ https://issues.apache.org/jira/browse/FOP-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2476: -- Flags: Patch Tagged pdf: Tags are showing inthe wrong order in the acrobat's pro order panel --- Key: FOP-2476 URL: https://issues.apache.org/jira/browse/FOP-2476 Project: FOP Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Attachments: after.pdf, before.pdf, fop.xconf, svnregionorder.patch, test.fo If you open before.pdf using acrobat pro, you can see tha the order that the tags appear in the order panel ( view- navigational panel --order or Advanced --accessibility -- TouchUp reading order) is incorrect, which creates issues with 508 compliance (section 3.2 http://www.hhs.gov/web/508/accessiblefiles/checklistpdf.html) . That is happening because of the order that content appears in the pdf content stream! By changing the order that the regions are rendered in AbstractRenderer this can be easily fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FOP-2476) Tagged pdf: Tags are showing inthe wrong order in the acrobat's pro order panel
Thanasis Giannimaras created FOP-2476: - Summary: Tagged pdf: Tags are showing inthe wrong order in the acrobat's pro order panel Key: FOP-2476 URL: https://issues.apache.org/jira/browse/FOP-2476 Project: FOP Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras If you open before.pdf using acrobat pro, you can see tha the order that the tags appear in the order panel ( view- navigational panel --order or Advanced --accessibility -- TouchUp reading order) is incorrect, which creates issues with 508 compliance (section 3.2 http://www.hhs.gov/web/508/accessiblefiles/checklistpdf.html) . That is happening because of the order that content appears in the pdf content stream! By changing the order that the regions are rendered in AbstractRenderer this can be easily fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2475) Tagged PDF footnote separator incorrect order
[ https://issues.apache.org/jira/browse/FOP-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2475: -- Flags: Patch Tagged PDF footnote separator incorrect order -- Key: FOP-2475 URL: https://issues.apache.org/jira/browse/FOP-2475 Project: FOP Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Attachments: after.pdf, before.pdf, footSep.patch, fop.xconf, test.fo For most cases footnote separator is being treated as an artifact so this is a non issue. But in cases where you have text working as footnote separator and not being labelled as an artifact, then the read out loud function (acrobat reader) reads it in the wrong order. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2474) AFP Logical element tag incorrect character encoding
[ https://issues.apache.org/jira/browse/FOP-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2474: -- Flags: Patch AFP Logical element tag incorrect character encoding Key: FOP-2474 URL: https://issues.apache.org/jira/browse/FOP-2474 Project: FOP Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Attachments: test.fo, tleEncoding.patch, trunk.afp, trunkFix.afp The dollar sign in the attribute value of the Tag Logical Element Structure, is not being displayed correctly (the cent sign is being showed instead). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2436) [PATCH] Merging of Tagged (Accessible) PDF
[ https://issues.apache.org/jira/browse/FOP-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2436: -- Attachment: newfop2.patch [PATCH] Merging of Tagged (Accessible) PDF -- Key: FOP-2436 URL: https://issues.apache.org/jira/browse/FOP-2436 Project: Fop Issue Type: New Feature Reporter: Thanasis Giannimaras Attachments: example.pdf, exemple.pdf, fop.patch, fop.xconf, newfop2.patch, pdfplugin.patch, pdfplugin2.patch, pdfpluginbinary2.zip, pdfpluginbinaryfiles.zip, test.fo, test2.fo This patch allows the merging of Tagged PDF. Known Limitations : -Only PDF with marked-content sequences in the page content stream are supported. Marked-content sequences in content stream other than the content stream of the page are not supported. -Repeated headers and footers are not completely supported. Example: 2-page pdf including table that spans both pages with repeated header. If you merge the second page, the table header will be visible in the pdf but the reader will ignore it (same principle applies for repeated footers). In order to use this feature, accessibility must be enabled in the configuration file and the source pdf must be accessible (tagged). The fo, configuration and the source pdf of a simple example is included. Also included, are the pdf-plugin junit tests. Necessary jars and pdf are included in the pdfpluginbinaryfiles zip. Branch: https://svn.apache.org/repos/asf/xmlgraphics/fop-pdf-images/branches/Temp_MergeTaggedPDF -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (FOP-2436) [PATCH] Merging of Tagged (Accessible) PDF
[ https://issues.apache.org/jira/browse/FOP-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550372#comment-14550372 ] Thanasis Giannimaras edited comment on FOP-2436 at 5/19/15 1:51 PM: Added newfop2 and pdfplugin2 patches to fix known issues with merging of tagged pdf code (junit tests are included) . Also Included the a new test case (exemple.pdf) that was flagged as not being tagged correctly. was (Author: agiannimaras): Added fop2 and pdfplugin2 patches to fix known issues with merging of tagged pdf code (junit tests are included) . Also Included the a new test case (exemple.pdf) that was flagged as not being tagged correctly. [PATCH] Merging of Tagged (Accessible) PDF -- Key: FOP-2436 URL: https://issues.apache.org/jira/browse/FOP-2436 Project: Fop Issue Type: New Feature Reporter: Thanasis Giannimaras Attachments: example.pdf, exemple.pdf, fop.patch, fop.xconf, newfop2.patch, pdfplugin.patch, pdfplugin2.patch, pdfpluginbinary2.zip, pdfpluginbinaryfiles.zip, test.fo, test2.fo This patch allows the merging of Tagged PDF. Known Limitations : -Only PDF with marked-content sequences in the page content stream are supported. Marked-content sequences in content stream other than the content stream of the page are not supported. -Repeated headers and footers are not completely supported. Example: 2-page pdf including table that spans both pages with repeated header. If you merge the second page, the table header will be visible in the pdf but the reader will ignore it (same principle applies for repeated footers). In order to use this feature, accessibility must be enabled in the configuration file and the source pdf must be accessible (tagged). The fo, configuration and the source pdf of a simple example is included. Also included, are the pdf-plugin junit tests. Necessary jars and pdf are included in the pdfpluginbinaryfiles zip. Branch: https://svn.apache.org/repos/asf/xmlgraphics/fop-pdf-images/branches/Temp_MergeTaggedPDF -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2436) [PATCH] Merging of Tagged (Accessible) PDF
[ https://issues.apache.org/jira/browse/FOP-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550372#comment-14550372 ] Thanasis Giannimaras commented on FOP-2436: --- Added fop2 and pdfplugin2 patches to fix known issues with merging of tagged pdf code (junit tests are included) . Also Included the a new test case (exemple.pdf) that was flagged as not being tagged correctly. [PATCH] Merging of Tagged (Accessible) PDF -- Key: FOP-2436 URL: https://issues.apache.org/jira/browse/FOP-2436 Project: Fop Issue Type: New Feature Reporter: Thanasis Giannimaras Attachments: example.pdf, exemple.pdf, fop.patch, fop.xconf, fop2.patch, pdfplugin.patch, pdfplugin2.patch, pdfpluginbinary2.zip, pdfpluginbinaryfiles.zip, test.fo, test2.fo This patch allows the merging of Tagged PDF. Known Limitations : -Only PDF with marked-content sequences in the page content stream are supported. Marked-content sequences in content stream other than the content stream of the page are not supported. -Repeated headers and footers are not completely supported. Example: 2-page pdf including table that spans both pages with repeated header. If you merge the second page, the table header will be visible in the pdf but the reader will ignore it (same principle applies for repeated footers). In order to use this feature, accessibility must be enabled in the configuration file and the source pdf must be accessible (tagged). The fo, configuration and the source pdf of a simple example is included. Also included, are the pdf-plugin junit tests. Necessary jars and pdf are included in the pdfpluginbinaryfiles zip. Branch: https://svn.apache.org/repos/asf/xmlgraphics/fop-pdf-images/branches/Temp_MergeTaggedPDF -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2436) [PATCH] Merging of Tagged (Accessible) PDF
[ https://issues.apache.org/jira/browse/FOP-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2436: -- Attachment: (was: fop2.patch) [PATCH] Merging of Tagged (Accessible) PDF -- Key: FOP-2436 URL: https://issues.apache.org/jira/browse/FOP-2436 Project: Fop Issue Type: New Feature Reporter: Thanasis Giannimaras Attachments: example.pdf, exemple.pdf, fop.patch, fop.xconf, pdfplugin.patch, pdfplugin2.patch, pdfpluginbinary2.zip, pdfpluginbinaryfiles.zip, test.fo, test2.fo This patch allows the merging of Tagged PDF. Known Limitations : -Only PDF with marked-content sequences in the page content stream are supported. Marked-content sequences in content stream other than the content stream of the page are not supported. -Repeated headers and footers are not completely supported. Example: 2-page pdf including table that spans both pages with repeated header. If you merge the second page, the table header will be visible in the pdf but the reader will ignore it (same principle applies for repeated footers). In order to use this feature, accessibility must be enabled in the configuration file and the source pdf must be accessible (tagged). The fo, configuration and the source pdf of a simple example is included. Also included, are the pdf-plugin junit tests. Necessary jars and pdf are included in the pdfpluginbinaryfiles zip. Branch: https://svn.apache.org/repos/asf/xmlgraphics/fop-pdf-images/branches/Temp_MergeTaggedPDF -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2436) [PATCH] Merging of Tagged (Accessible) PDF
[ https://issues.apache.org/jira/browse/FOP-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2436: -- Attachment: pdfpluginbinary2.zip pdfplugin2.patch fop2.patch [PATCH] Merging of Tagged (Accessible) PDF -- Key: FOP-2436 URL: https://issues.apache.org/jira/browse/FOP-2436 Project: Fop Issue Type: New Feature Reporter: Thanasis Giannimaras Attachments: example.pdf, exemple.pdf, fop.patch, fop.xconf, fop2.patch, pdfplugin.patch, pdfplugin2.patch, pdfpluginbinary2.zip, pdfpluginbinaryfiles.zip, test.fo, test2.fo This patch allows the merging of Tagged PDF. Known Limitations : -Only PDF with marked-content sequences in the page content stream are supported. Marked-content sequences in content stream other than the content stream of the page are not supported. -Repeated headers and footers are not completely supported. Example: 2-page pdf including table that spans both pages with repeated header. If you merge the second page, the table header will be visible in the pdf but the reader will ignore it (same principle applies for repeated footers). In order to use this feature, accessibility must be enabled in the configuration file and the source pdf must be accessible (tagged). The fo, configuration and the source pdf of a simple example is included. Also included, are the pdf-plugin junit tests. Necessary jars and pdf are included in the pdfpluginbinaryfiles zip. Branch: https://svn.apache.org/repos/asf/xmlgraphics/fop-pdf-images/branches/Temp_MergeTaggedPDF -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2436) [PATCH] Merging of Tagged (Accessible) PDF
[ https://issues.apache.org/jira/browse/FOP-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2436: -- Attachment: test2.fo exemple.pdf [PATCH] Merging of Tagged (Accessible) PDF -- Key: FOP-2436 URL: https://issues.apache.org/jira/browse/FOP-2436 Project: Fop Issue Type: New Feature Reporter: Thanasis Giannimaras Attachments: example.pdf, exemple.pdf, fop.patch, fop.xconf, pdfplugin.patch, pdfpluginbinaryfiles.zip, test.fo, test2.fo This patch allows the merging of Tagged PDF. Known Limitations : -Only PDF with marked-content sequences in the page content stream are supported. Marked-content sequences in content stream other than the content stream of the page are not supported. -Repeated headers and footers are not completely supported. Example: 2-page pdf including table that spans both pages with repeated header. If you merge the second page, the table header will be visible in the pdf but the reader will ignore it (same principle applies for repeated footers). In order to use this feature, accessibility must be enabled in the configuration file and the source pdf must be accessible (tagged). The fo, configuration and the source pdf of a simple example is included. Also included, are the pdf-plugin junit tests. Necessary jars and pdf are included in the pdfpluginbinaryfiles zip. Branch: https://svn.apache.org/repos/asf/xmlgraphics/fop-pdf-images/branches/Temp_MergeTaggedPDF -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2442) New accessibility feature: Specifying the expansion of an abbreviation
[ https://issues.apache.org/jira/browse/FOP-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2442: -- Attachment: fop.xconf fop.patch test.fo test.pdf New accessibility feature: Specifying the expansion of an abbreviation -- Key: FOP-2442 URL: https://issues.apache.org/jira/browse/FOP-2442 Project: Fop Issue Type: New Feature Affects Versions: trunk Reporter: Thanasis Giannimaras Attachments: fop.patch, fop.xconf, test.fo, test.pdf This patch introduces a new extension property fox:abbreviation (applies to fo:inline element) that allows the user to choose how abbreviations will be resolved by the screen reader -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FOP-2442) New accessibility feature: Specifying the expansion of an abbreviation
Thanasis Giannimaras created FOP-2442: - Summary: New accessibility feature: Specifying the expansion of an abbreviation Key: FOP-2442 URL: https://issues.apache.org/jira/browse/FOP-2442 Project: Fop Issue Type: New Feature Affects Versions: trunk Reporter: Thanasis Giannimaras This patch introduces a new extension property fox:abbreviation (applies to fo:inline element) that allows the user to choose how abbreviations will be resolved by the screen reader -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2443) Repeated Table headers and footers with markers are not being treated as artifacts
[ https://issues.apache.org/jira/browse/FOP-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2443: -- Attachment: fop.xconf fop.patch test.fo testBefore.pdf testAfter.pdf Repeated Table headers and footers with markers are not being treated as artifacts -- Key: FOP-2443 URL: https://issues.apache.org/jira/browse/FOP-2443 Project: Fop Issue Type: Bug Reporter: Thanasis Giannimaras Fix For: trunk Attachments: fop.patch, fop.xconf, test.fo, testAfter.pdf, testBefore.pdf When accessibility is enabled, repeated table headers and footers with markers are not being treated as artifacts, resulting to be read out multiple times, when a screen reader is used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FOP-2443) Repeated Table headers and footers with markers are not being treated as artifacts
Thanasis Giannimaras created FOP-2443: - Summary: Repeated Table headers and footers with markers are not being treated as artifacts Key: FOP-2443 URL: https://issues.apache.org/jira/browse/FOP-2443 Project: Fop Issue Type: Bug Reporter: Thanasis Giannimaras Fix For: trunk When accessibility is enabled, repeated table headers and footers with markers are not being treated as artifacts, resulting to be read out multiple times, when a screen reader is used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2441) pdf:embedded-file extension is broken, gives NullPointerException
[ https://issues.apache.org/jira/browse/FOP-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14291713#comment-14291713 ] Thanasis Giannimaras commented on FOP-2441: --- Duplicate of FOP-2348 https://issues.apache.org/jira/browse/FOP-2348 pdf:embedded-file extension is broken, gives NullPointerException - Key: FOP-2441 URL: https://issues.apache.org/jira/browse/FOP-2441 Project: Fop Issue Type: Bug Components: renderer/pdf Affects Versions: trunk Reporter: Luca Furini Priority: Minor Attachments: change.diff, test_attachment.fo The extension property pdf:embedded-file (to attach files to the pdf) is not working, and generates a NullPointerException. I noticed the problem while trying to write an answer to this StackOverflow question: http://stackoverflow.com/questions/28110607/unable-to-add-an-attachment-to-a-pdf-while-using-fop (the question is about a different problem, but while testing on fop-trunk I noticed this bug I'm reporting). Looking at the revision history, I think the implementation of this extension has been broken since revision [1522934]. I'm going to attach a simple fo file showing the problem, together with a proposed patch. I have been a fop committer for some time, followed by a looong period of just lurking the mailing list; I tried to commit the changes myself, but I guess my long inactivity period has caused the revocation of my commit privileges. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2439) Using number-rows-spanned results in a ValidationException
[ https://issues.apache.org/jira/browse/FOP-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14274973#comment-14274973 ] Thanasis Giannimaras commented on FOP-2439: --- I may be wrong but I think even in the second example you have the same issue. In the second row there are 2 cells ( the first cell in the table that spans two rows and and one empty cell). If you add another fo :table- colum element or you comment them out entirely, you do not get an error (at least with fop-trunk). Thanasis Using number-rows-spanned results in a ValidationException -- Key: FOP-2439 URL: https://issues.apache.org/jira/browse/FOP-2439 Project: Fop Issue Type: Bug Components: renderer/pdf Affects Versions: 1.1 Environment: Windows 8.1 Reporter: nick.heyworth Priority: Critical Attachments: Possible FOP Bug Modified.fo, Possible FOP Bug.fo The attached file results in a ValidationException when attempting to create PDF. After changing the value of the number-rows-spanned attribute to 1, PDF creation works. In case my FO is incorrect, please let me know. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FOP-2436) Merging of Tagged (Accessible) PDF
Thanasis Giannimaras created FOP-2436: - Summary: Merging of Tagged (Accessible) PDF Key: FOP-2436 URL: https://issues.apache.org/jira/browse/FOP-2436 Project: Fop Issue Type: New Feature Reporter: Thanasis Giannimaras This patch allows the merging of Tagged PDF. Known Limitations : -Only PDF with marked-content sequences in the page content stream are supported. Marked-content sequences in content stream other than the content stream of the page are not supported. -Repeated headers and footers are not completely supported. Example: 2-page pdf including table that spans both pages with repeated header. If you merge the second page, the table header will be visible in the pdf but the reader will ignore it (same principle applies for repeated footers). In order to use this feature, accessibility must be enabled in the configuration file and the source pdf must be accessible (tagged). The fo, configuration and the source pdf of a simple example is included. Also included, are the pdf-plugin junit tests. Necessary jars and pdf are included in the pdfpluginbinaryfiles zip. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2436) Merging of Tagged (Accessible) PDF
[ https://issues.apache.org/jira/browse/FOP-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2436: -- Attachment: test.fo fop.xconf example.pdf pdfpluginbinaryfiles.zip pdfplugin.patch fop.patch Merging of Tagged (Accessible) PDF -- Key: FOP-2436 URL: https://issues.apache.org/jira/browse/FOP-2436 Project: Fop Issue Type: New Feature Reporter: Thanasis Giannimaras Attachments: example.pdf, fop.patch, fop.xconf, pdfplugin.patch, pdfpluginbinaryfiles.zip, test.fo This patch allows the merging of Tagged PDF. Known Limitations : -Only PDF with marked-content sequences in the page content stream are supported. Marked-content sequences in content stream other than the content stream of the page are not supported. -Repeated headers and footers are not completely supported. Example: 2-page pdf including table that spans both pages with repeated header. If you merge the second page, the table header will be visible in the pdf but the reader will ignore it (same principle applies for repeated footers). In order to use this feature, accessibility must be enabled in the configuration file and the source pdf must be accessible (tagged). The fo, configuration and the source pdf of a simple example is included. Also included, are the pdf-plugin junit tests. Necessary jars and pdf are included in the pdfpluginbinaryfiles zip. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2432) OTF font NPE
[ https://issues.apache.org/jira/browse/FOP-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2432: -- Attachment: testOTF.fo OTF font NPE - Key: FOP-2432 URL: https://issues.apache.org/jira/browse/FOP-2432 Project: Fop Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Priority: Minor Attachments: SourceSansProBold.otf, expected.if.xml, fop.xconf, otfNullException.patch, testOTF.fo Intermediate Format to Postscript results to an NPE when otf fonts are used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2432) OTF font NPE
[ https://issues.apache.org/jira/browse/FOP-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229240#comment-14229240 ] Thanasis Giannimaras commented on FOP-2432: --- Tested on Trunk OTF font NPE - Key: FOP-2432 URL: https://issues.apache.org/jira/browse/FOP-2432 Project: Fop Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Priority: Minor Attachments: SourceSansProBold.otf, expected.if.xml, fop.xconf, otfNullException.patch, stack.txt, testOTF.fo Intermediate Format to Postscript results to an NPE when otf fonts are used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2432) OTF font NPE
[ https://issues.apache.org/jira/browse/FOP-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2432: -- Attachment: stack.txt OTF font NPE - Key: FOP-2432 URL: https://issues.apache.org/jira/browse/FOP-2432 Project: Fop Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Priority: Minor Attachments: SourceSansProBold.otf, expected.if.xml, fop.xconf, otfNullException.patch, stack.txt, testOTF.fo Intermediate Format to Postscript results to an NPE when otf fonts are used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FOP-2432) OTF font NPE
Thanasis Giannimaras created FOP-2432: - Summary: OTF font NPE Key: FOP-2432 URL: https://issues.apache.org/jira/browse/FOP-2432 Project: Fop Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Priority: Minor Intermediate Format to Postscript results to an NPE when otf fonts are used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2432) OTF font NPE
[ https://issues.apache.org/jira/browse/FOP-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2432: -- Attachment: expected.if.xml OTF font NPE - Key: FOP-2432 URL: https://issues.apache.org/jira/browse/FOP-2432 Project: Fop Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Priority: Minor Attachments: expected.if.xml Intermediate Format to Postscript results to an NPE when otf fonts are used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2432) OTF font NPE
[ https://issues.apache.org/jira/browse/FOP-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2432: -- Attachment: fop.xconf OTF font NPE - Key: FOP-2432 URL: https://issues.apache.org/jira/browse/FOP-2432 Project: Fop Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Priority: Minor Attachments: SourceSansProBold.otf, expected.if.xml, fop.xconf Intermediate Format to Postscript results to an NPE when otf fonts are used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2432) OTF font NPE
[ https://issues.apache.org/jira/browse/FOP-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2432: -- Attachment: SourceSansProBold.otf OTF font NPE - Key: FOP-2432 URL: https://issues.apache.org/jira/browse/FOP-2432 Project: Fop Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Priority: Minor Attachments: SourceSansProBold.otf, expected.if.xml, fop.xconf Intermediate Format to Postscript results to an NPE when otf fonts are used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2432) OTF font NPE
[ https://issues.apache.org/jira/browse/FOP-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2432: -- Attachment: otfNullException.patch Small patch that fix the issue OTF font NPE - Key: FOP-2432 URL: https://issues.apache.org/jira/browse/FOP-2432 Project: Fop Issue Type: Bug Affects Versions: trunk Reporter: Thanasis Giannimaras Priority: Minor Attachments: SourceSansProBold.otf, expected.if.xml, fop.xconf, otfNullException.patch Intermediate Format to Postscript results to an NPE when otf fonts are used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2281) factory is not initialized when -cache is used in org.apache.fop.cli.Main
[ https://issues.apache.org/jira/browse/FOP-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14193795#comment-14193795 ] Thanasis Giannimaras commented on FOP-2281: --- Small fix for the NPE factory is not initialized when -cache is used in org.apache.fop.cli.Main - Key: FOP-2281 URL: https://issues.apache.org/jira/browse/FOP-2281 Project: Fop Issue Type: Bug Environment: Fedora 19 64 bit Reporter: Leo Fix For: trunk 1.I set all jar files in the classpath. 2. I run this command java org.apache.fop.cli.Main -cache cacheFile NullPointerException occurs. The variable factory in CommandLineOptions is not initialized -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (FOP-2281) factory is not initialized when -cache is used in org.apache.fop.cli.Main
[ https://issues.apache.org/jira/browse/FOP-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2281: -- Comment: was deleted (was: Small fix for the NPE) factory is not initialized when -cache is used in org.apache.fop.cli.Main - Key: FOP-2281 URL: https://issues.apache.org/jira/browse/FOP-2281 Project: Fop Issue Type: Bug Environment: Fedora 19 64 bit Reporter: Leo Fix For: trunk 1.I set all jar files in the classpath. 2. I run this command java org.apache.fop.cli.Main -cache cacheFile NullPointerException occurs. The variable factory in CommandLineOptions is not initialized -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2281) factory is not initialized when -cache is used in org.apache.fop.cli.Main
[ https://issues.apache.org/jira/browse/FOP-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2281: -- Attachment: fop2281.patch Small fix for the NPE factory is not initialized when -cache is used in org.apache.fop.cli.Main - Key: FOP-2281 URL: https://issues.apache.org/jira/browse/FOP-2281 Project: Fop Issue Type: Bug Environment: Fedora 19 64 bit Reporter: Leo Fix For: trunk Attachments: fop2281.patch 1.I set all jar files in the classpath. 2. I run this command java org.apache.fop.cli.Main -cache cacheFile NullPointerException occurs. The variable factory in CommandLineOptions is not initialized -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2405) Footnote in Table Header Ignored
[ https://issues.apache.org/jira/browse/FOP-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2405: -- Attachment: testTrunk.pdf test1.1.pdf Footnote in Table Header Ignored Key: FOP-2405 URL: https://issues.apache.org/jira/browse/FOP-2405 Project: Fop Issue Type: Bug Affects Versions: 1.1 Environment: Windows 8.1 Reporter: nick.heyworth Attachments: Footnote in Table Header.fo, test1.1.pdf, testTrunk.pdf See the attached FO file. It creates a table with a header row and a body row with one cell each, and a footnote in each cell. The footnote in the header cell fails to render. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FOP-2405) Footnote in Table Header Ignored
[ https://issues.apache.org/jira/browse/FOP-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14092698#comment-14092698 ] Thanasis Giannimaras commented on FOP-2405: --- The issue seems to be fixed on trunk (see included attachments test1.1 and testTrunk created by Footnote in table Header.fo) Footnote in Table Header Ignored Key: FOP-2405 URL: https://issues.apache.org/jira/browse/FOP-2405 Project: Fop Issue Type: Bug Affects Versions: 1.1 Environment: Windows 8.1 Reporter: nick.heyworth Attachments: Footnote in Table Header.fo, test1.1.pdf, testTrunk.pdf See the attached FO file. It creates a table with a header row and a body row with one cell each, and a footnote in each cell. The footnote in the header cell fails to render. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FOP-2399) External graphics that return 403 error, make FOP crash
[ https://issues.apache.org/jira/browse/FOP-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14079186#comment-14079186 ] Thanasis Giannimaras commented on FOP-2399: --- I am unable to reproduce the issue both on fop1.1 and on trunk. FOP doesn't crash, it just renders the PDF without the image (which can not access because of the 403 error). The warnings I am getting when running fop1.1 are : Jul 30, 2014 11:51:20 AM org.apache.fop.apps.FOURIResolver resolve SEVERE: Error with opening URL 'http://192.168.3.200/image1.png': Server returned HTTP response code: 403 for URL: http://192.168.3.200/image1.png Jul 30, 2014 11:51:20 AM org.apache.fop.events.LoggingEventListener processEvent SEVERE: Image not found. URI: http://192.168.3.200/image1.png. (See position 12:80) Jul 30, 2014 11:51:20 AM org.apache.fop.events.LoggingEventListener processEvent INFO: Rendered page #1. External graphics that return 403 error, make FOP crash --- Key: FOP-2399 URL: https://issues.apache.org/jira/browse/FOP-2399 Project: Fop Issue Type: Bug Components: image/unqualified Affects Versions: 1.1 Reporter: Konstantin Milyutin Labels: external-graphic Attachments: stack I use external-graphics tag in my template. When a graphic is not found (404 response code), the pdf is rendered without a graphic. On the other hand, when the response code is 403 (not authorized), then the FOP crashes with EOF exception somewhere in graphics library. The referenced resource doesn't have to be an image. It can even be just simple page, returning 403 error code. I think the same error also happens when response code is 401. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (FOP-2297) Degraded output from SVG external graphic on upgrade from fop-1.0 to fop-1.1
[ https://issues.apache.org/jira/browse/FOP-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911425#comment-13911425 ] Thanasis Giannimaras edited comment on FOP-2297 at 5/21/14 3:24 PM: I think the regression was introduced in revision number 987423, (iintroducing changes in the PDFImageHandlerSVG class). I have attached two pdf files that show the difference in the svg output, by using revision 987423 and 987422. was (Author: agiannimaras): I think the regression was introduced in revision number 987423, (iintroducing changes in the PDFImageHandlerSVG class). I have attached two pdf files that show the difference in the svg output, by using revision 987423 and 9874220 Degraded output from SVG external graphic on upgrade from fop-1.0 to fop-1.1 Key: FOP-2297 URL: https://issues.apache.org/jira/browse/FOP-2297 Project: Fop Issue Type: Bug Components: svg Affects Versions: 1.1, trunk Environment: Verified on both MacOSX and Win32. Reporter: Glenn Adams Attachments: Google.svg, svg-flattening-1.0.pdf, svg-flattening-1.1.pdf, svg-flattening.fo, test.bad.pdf, test.fo.xml, test.good.pdf, test987422.pdf, test987423.pdf When updating from JDK 1.7.0_21 to 1.7.0_25, PDF output of SVG external graphics appears to switch to low resolution, poor rendering quality. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FOP-2297) Degraded output from SVG external graphic on upgrade from fop-1.0 to fop-1.1
[ https://issues.apache.org/jira/browse/FOP-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-2297: -- Attachment: test987423.pdf test987422.pdf Degraded output from SVG external graphic on upgrade from fop-1.0 to fop-1.1 Key: FOP-2297 URL: https://issues.apache.org/jira/browse/FOP-2297 Project: Fop Issue Type: Bug Components: svg Affects Versions: 1.1, trunk Environment: Verified on both MacOSX and Win32. Reporter: Glenn Adams Attachments: Google.svg, test.bad.pdf, test.fo.xml, test.good.pdf, test987422.pdf, test987423.pdf When updating from JDK 1.7.0_21 to 1.7.0_25, PDF output of SVG external graphics appears to switch to low resolution, poor rendering quality. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (FOP-1342) Incorrect rendering of GIF images
[ https://issues.apache.org/jira/browse/FOP-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-1342: -- Attachment: gif_scale.patch Fix incorrect rendering of GIF image. Use of ImageIO class to read the correct dimensions of the image. Previously, it read the values taken by the Logical Screen descriptor (canvas width and height), which is not always correct because a gif file can have more than one images. The correct width and height values are included in the Image Descriptor block. Incorrect rendering of GIF images - Key: FOP-1342 URL: https://issues.apache.org/jira/browse/FOP-1342 Project: Fop Issue Type: Bug Components: images Affects Versions: trunk Environment: Operating System: other Platform: Other Reporter: Trejkaz Attachments: fop-gif-scaling-bug.zip, gif_scale.patch, imageio-size-fix.patch Attached zip file contains an example with a single GIF, which exhibits two problems: 1. the GIF is scaled in a strange fashion, and 2. the black lines are lost. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (FOP-1342) Incorrect rendering of GIF images
[ https://issues.apache.org/jira/browse/FOP-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-1342: -- Attachment: gif_scale.patch Incorrect rendering of GIF images - Key: FOP-1342 URL: https://issues.apache.org/jira/browse/FOP-1342 Project: Fop Issue Type: Bug Components: images Affects Versions: trunk Environment: Operating System: other Platform: Other Reporter: Trejkaz Attachments: fop-gif-scaling-bug.zip, imageio-size-fix.patch, scale.patch Attached zip file contains an example with a single GIF, which exhibits two problems: 1. the GIF is scaled in a strange fashion, and 2. the black lines are lost. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (FOP-1342) Incorrect rendering of GIF images
[ https://issues.apache.org/jira/browse/FOP-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-1342: -- Attachment: (was: gif_scale.patch) Incorrect rendering of GIF images - Key: FOP-1342 URL: https://issues.apache.org/jira/browse/FOP-1342 Project: Fop Issue Type: Bug Components: images Affects Versions: trunk Environment: Operating System: other Platform: Other Reporter: Trejkaz Attachments: fop-gif-scaling-bug.zip, imageio-size-fix.patch, scale.patch Attached zip file contains an example with a single GIF, which exhibits two problems: 1. the GIF is scaled in a strange fashion, and 2. the black lines are lost. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (FOP-1342) Incorrect rendering of GIF images
[ https://issues.apache.org/jira/browse/FOP-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-1342: -- Attachment: (was: gif_scale.patch) Incorrect rendering of GIF images - Key: FOP-1342 URL: https://issues.apache.org/jira/browse/FOP-1342 Project: Fop Issue Type: Bug Components: images Affects Versions: trunk Environment: Operating System: other Platform: Other Reporter: Trejkaz Attachments: fop-gif-scaling-bug.zip, imageio-size-fix.patch, scale.patch Attached zip file contains an example with a single GIF, which exhibits two problems: 1. the GIF is scaled in a strange fashion, and 2. the black lines are lost. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (FOP-1342) Incorrect rendering of GIF images
[ https://issues.apache.org/jira/browse/FOP-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-1342: -- Attachment: scale.patch Incorrect rendering of GIF images - Key: FOP-1342 URL: https://issues.apache.org/jira/browse/FOP-1342 Project: Fop Issue Type: Bug Components: images Affects Versions: trunk Environment: Operating System: other Platform: Other Reporter: Trejkaz Attachments: fop-gif-scaling-bug.zip, imageio-size-fix.patch, scale.patch Attached zip file contains an example with a single GIF, which exhibits two problems: 1. the GIF is scaled in a strange fashion, and 2. the black lines are lost. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (FOP-1801) conversion BW GIF=PDF creates PDF with colorspace RGB if FOP0.95 and Gray if FOP0.20.5
[ https://issues.apache.org/jira/browse/FOP-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-1801: -- Attachment: xgc.patch weather.gif test.fo fop.patch Following Jeremias instructions , I first check if all the palette entries have the same value and if yes then use /DeviceGray instead of DeviceRGB . The fop.patch includes changes in fop (AbstractImageAdapter class) necessary for the generation of PDF with DeviceGray, whereas the xgc patch contain changes necessary for the creation of PS files (again when all palette entries have the same value). conversion BW GIF=PDF creates PDF with colorspace RGB if FOP0.95 and Gray if FOP0.20.5 Key: FOP-1801 URL: https://issues.apache.org/jira/browse/FOP-1801 Project: Fop Issue Type: Bug Components: awt renderer Affects Versions: 0.95 Environment: Operating System: Linux Platform: Other Reporter: Isidora Attachments: fop.patch, test.fo, weather.gif, xgc.patch Even though the PDFs obtained with both FOP versions look and print OK, when the one created with 0.95 is pushed through the FAX system, the image obtained contains dotted areas that correspond to white areas in the PDF created with 0.20.5. I posted the question to FOP forum and Jeremias Maerki helped me research the issue. If the PDF with problems is manipulated by : changing /ColorSpace [/Indexed /DeviceRGB 1 FF00] to: /ColorSpace [/Indexed /DeviceGray 1 FF00 the dotted areas go back to be white areas. i.e. the problem is resolved by this change When I asked him if I could make this change in colorspace from inside my XSL-FO he responded: If you want this kind of functionality, it has to be fixed in Java code first.If you want to give this a try, the place to fix this is: org.apache.fop.render.pdf.ImageRenderedAdapter.populateXObjectDictionary(PDFDictionary) There, a check has to be implemented to see if all palette entries are plain grayscale values (red, green and blue all the same) in which case /DeviceGray can be specified instead of /DeviceRGB. And of course, the palette entries need to be 8bit rather than 24bits then. My expertise in manipulating colors and graphics is not big enough for me to make changes to this code. So, I hope someone with more knowledge could fix this bug. Thank you -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (FOP-1872) External document is clipped when rotated
[ https://issues.apache.org/jira/browse/FOP-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thanasis Giannimaras updated FOP-1872: -- Attachment: FOP-1872.patch External document is clipped when rotated, because IPD and BPD values are being set incorrectly in the ExternalDocumentLayoutManager class, without taking into account the reference orientation value. External document is clipped when rotated - Key: FOP-1872 URL: https://issues.apache.org/jira/browse/FOP-1872 Project: Fop Issue Type: Bug Components: pdf Affects Versions: 1.0 Environment: Operating System: Linux Platform: PC Reporter: Krister Wicksell Attachments: FOP-1872.patch, landscape.fo, landscape.pdf, portrait.fo, portrait.pdf When I use fox:external-document and a reference-orientation of 90 degrees the content is clipped to width of the page. The external document is A4 landscape so I rotate it to get it as portrait. So the document is rotated and the page size is correct but the content of the page is clipped and don't fill the whole height. I have traced the problem to ExternalDocumentLayoutManager.createPage(...). I think the line: RegionViewport rv = new RegionViewport(referenceRect); should be replaced by: RegionViewport rv = new RegionViewport(new Rectangle(0, 0, imageSize.width, imageSize.height)); Is this correct? -- This message was sent by Atlassian JIRA (v6.1#6144)
