[jira] [Updated] (FOP-3155) Font merged from external pdf may not print
[ https://issues.apache.org/jira/browse/FOP-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3155: --- Attachment: Adverse_impact_addendum.pdf fop.xconf simple.fo > Font merged from external pdf may not print > --- > > Key: FOP-3155 > URL: https://issues.apache.org/jira/browse/FOP-3155 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: Adverse_impact_addendum.pdf, fop.xconf, simple.fo > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3155) Font merged from external pdf may not print
Simon Steiner created FOP-3155: -- Summary: Font merged from external pdf may not print Key: FOP-3155 URL: https://issues.apache.org/jira/browse/FOP-3155 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FOP-3154) Concurrency problem when rendering document
[
https://issues.apache.org/jira/browse/FOP-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17774991#comment-17774991
]
Simon Steiner commented on FOP-3154:
You will need to have each thread have its own instance of the fopfactory
> Concurrency problem when rendering document
> ---
>
> Key: FOP-3154
> URL: https://issues.apache.org/jira/browse/FOP-3154
> Project: FOP
> Issue Type: Bug
> Components: renderer/awt
>Affects Versions: 2.9
> Environment: Windows 11
> Java:
> openjdk version "1.8.0_312"
> openjdk version "17.0.5" 2022-10-18
>Reporter: George Lindholm
>Priority: Major
> Attachments: fop.log, tran.xml
>
>
> Hi,
> I've been working on upgrading our ancient use of fop (0.20.5) to the
> latest version of xmlgraphics (2.9) but I've been stymied by a concurrency
> problem that causes a FOPException
> {{org.apache.fop.apps.FOPException: Requested page number is out of range: 0;
> only 0 page(s) available.}}
> Complicating the issue is that when I try to debug the workflow the problem
> does not happen. I've been able to trace part of the flow by using
> conditional breakpoints that prints to the console which has helped, but the
> more conditionals I put in, the less likely the problem shows up
> An extract of the log shows:
> I{{{}NFO: table-layout="fixed" and width="auto", but auto-layout not
> supported => assuming width="100%". (See position 201:18){}}}
> {{Thread[Thread-4,5,main]PreviewPanel.Reloader.run()}}
> {{Thread[AWT-EventQueue-0,6,main]Java2DRenderer.getPageViewport()}}
> {{org.apache.fop.apps.FOPException: Requested page number is out of range: 0;
> only 0 page(s) available.}}
> {{ at
> org.apache.fop.render.java2d.Java2DRenderer.getPageViewport(Java2DRenderer.java:421)}}
> {{ at
> org.apache.fop.render.java2d.Java2DRenderer.getPageImage(Java2DRenderer.java:436)}}
> {{ at
> org.apache.fop.render.awt.viewer.ImageProxyPanel.paintComponent(ImageProxyPanel.java:123)}}
> {{...}}
> {{INFO: table-layout="fixed" and width="auto", but auto-layout not supported
> => assuming width="100%". (See position 201:18)}}
> {{Thread[Thread-4,5,main]PreviewPanel.setPage()}}
> Somehow the AWT thread is dispatched while Reloader.run() is still running so
> the data is un-available to render.
> I run fop in Eclipse using the arguments: {{-awt tran.xml}}
> The only way I've been able to cause the issue is to keep running fop until
> it happens.
> Any insight would be appreciated
> George
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FOP-3150) Binary distribution used to include an executable jar file
[
https://issues.apache.org/jira/browse/FOP-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner resolved FOP-3150.
Fix Version/s: main
Resolution: Fixed
https://github.com/apache/xmlgraphics-fop/commit/699b56779e89d45ae8d8ea517bc7cee57e2f4231
> Binary distribution used to include an executable jar file
> --
>
> Key: FOP-3150
> URL: https://issues.apache.org/jira/browse/FOP-3150
> Project: FOP
> Issue Type: Bug
> Components: unqualified
>Affects Versions: 2.9
> Environment: Windows 10
>Reporter: Tom Habing
>Assignee: Simon Steiner
>Priority: Major
> Fix For: main
>
>
> With version 2.8 there was a single executable jar file in the build
> directory, allowing it to be run like so:
>
> {code:java}
> C:\Program Files\Apache FOP\fop-2.8\fop\build>java -jar fop.jar -version
> FOP Version 2.8{code}
> With version 2.9 this seems to no longer be the case. Now it seems like the
> full class path and the main class need to be specified on the command line:
> {code:java}
> C:\Program Files\Apache FOP\fop-2.9\fop\build>java -cp ";C:\Program
> Files\Apache FOP\fop-2.9\fop\build\fop-2.9.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\build\fop-core-2.9.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\build\fop-events-2.9.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\build\fop-util-2.9.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-anim-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-awt-util-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-bridge-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-codec-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-constants-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-css-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-dom-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-ext-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-extension-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-gvt-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-i18n-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-parser-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-script-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-shared-resources-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-svg-dom-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-svggen-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-transcoder-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-util-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-xml-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\commons-io-2.11.0.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\commons-logging-1.0.4.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\fontbox-2.0.27.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\xml-apis-1.4.01.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\xml-apis-ext-1.3.04.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\xmlgraphics-commons-2.9.jar" org.apache.fop.cli.Main
> -version
> FOP Version SVN{code}
>
> An executable jar file for 2.9 would be appreciated.
> Also, as you can see above, 2.9 does not report a valid version number.
> (I'll file a separate ticket for this.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FOP-3150) Binary distribution used to include an executable jar file
[
https://issues.apache.org/jira/browse/FOP-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner reassigned FOP-3150:
--
Assignee: Simon Steiner
> Binary distribution used to include an executable jar file
> --
>
> Key: FOP-3150
> URL: https://issues.apache.org/jira/browse/FOP-3150
> Project: FOP
> Issue Type: Bug
> Components: unqualified
>Affects Versions: 2.9
> Environment: Windows 10
>Reporter: Tom Habing
>Assignee: Simon Steiner
>Priority: Major
>
> With version 2.8 there was a single executable jar file in the build
> directory, allowing it to be run like so:
>
> {code:java}
> C:\Program Files\Apache FOP\fop-2.8\fop\build>java -jar fop.jar -version
> FOP Version 2.8{code}
> With version 2.9 this seems to no longer be the case. Now it seems like the
> full class path and the main class need to be specified on the command line:
> {code:java}
> C:\Program Files\Apache FOP\fop-2.9\fop\build>java -cp ";C:\Program
> Files\Apache FOP\fop-2.9\fop\build\fop-2.9.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\build\fop-core-2.9.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\build\fop-events-2.9.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\build\fop-util-2.9.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-anim-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-awt-util-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-bridge-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-codec-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-constants-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-css-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-dom-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-ext-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-extension-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-gvt-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-i18n-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-parser-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-script-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-shared-resources-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-svg-dom-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-svggen-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-transcoder-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-util-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-xml-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\commons-io-2.11.0.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\commons-logging-1.0.4.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\fontbox-2.0.27.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\xml-apis-1.4.01.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\xml-apis-ext-1.3.04.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\xmlgraphics-commons-2.9.jar" org.apache.fop.cli.Main
> -version
> FOP Version SVN{code}
>
> An executable jar file for 2.9 would be appreciated.
> Also, as you can see above, 2.9 does not report a valid version number.
> (I'll file a separate ticket for this.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FOP-3150) Binary distribution used to include an executable jar file
[
https://issues.apache.org/jira/browse/FOP-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765475#comment-17765475
]
Simon Steiner commented on FOP-3150:
What about using the fop.bat file
> Binary distribution used to include an executable jar file
> --
>
> Key: FOP-3150
> URL: https://issues.apache.org/jira/browse/FOP-3150
> Project: FOP
> Issue Type: Bug
> Components: unqualified
>Affects Versions: 2.9
> Environment: Windows 10
>Reporter: Tom Habing
>Priority: Major
>
> With version 2.8 there was a single executable jar file in the build
> directory, allowing it to be run like so:
>
> {code:java}
> C:\Program Files\Apache FOP\fop-2.8\fop\build>java -jar fop.jar -version
> FOP Version 2.8{code}
> With version 2.9 this seems to no longer be the case. Now it seems like the
> full class path and the main class need to be specified on the command line:
> {code:java}
> C:\Program Files\Apache FOP\fop-2.9\fop\build>java -cp ";C:\Program
> Files\Apache FOP\fop-2.9\fop\build\fop-2.9.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\build\fop-core-2.9.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\build\fop-events-2.9.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\build\fop-util-2.9.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-anim-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-awt-util-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-bridge-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-codec-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-constants-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-css-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-dom-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-ext-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-extension-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-gvt-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-i18n-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-parser-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-script-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-shared-resources-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-svg-dom-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-svggen-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-transcoder-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-util-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-xml-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\commons-io-2.11.0.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\commons-logging-1.0.4.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\fontbox-2.0.27.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\xml-apis-1.4.01.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\xml-apis-ext-1.3.04.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\xmlgraphics-commons-2.9.jar" org.apache.fop.cli.Main
> -version
> FOP Version SVN{code}
>
> An executable jar file for 2.9 would be appreciated.
> Also, as you can see above, 2.9 does not report a valid version number.
> (I'll file a separate ticket for this.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FOP-3151) FOP 2.9 '-version' param does not report correct version number
[
https://issues.apache.org/jira/browse/FOP-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner resolved FOP-3151.
Resolution: Duplicate
See FOP-3146
> FOP 2.9 '-version' param does not report correct version number
> ---
>
> Key: FOP-3151
> URL: https://issues.apache.org/jira/browse/FOP-3151
> Project: FOP
> Issue Type: Bug
> Components: unqualified
>Affects Versions: 2.9
>Reporter: Tom Habing
>Priority: Major
>
> {code:java}
> C:\Program Files\Apache FOP\fop-2.9\fop>fop -version
> FOP Version SVN{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FOP-3149) Don't merge fonts when ascent is different
[ https://issues.apache.org/jira/browse/FOP-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3149. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop-pdf-images/commit/228a801d4a85aa729703ae6acac73629d4dd9ac5 > Don't merge fonts when ascent is different > -- > > Key: FOP-3149 > URL: https://issues.apache.org/jira/browse/FOP-3149 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > Attachments: fop.xconf, test.fo > > > fop test.fo -c fop.xconf out.pdf > Output font size should match input pdf -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3149) Don't merge fonts when ascent is different
[ https://issues.apache.org/jira/browse/FOP-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3149: --- Description: fop test.fo -c fop.xconf out.pdf Output font size should match input pdf > Don't merge fonts when ascent is different > -- > > Key: FOP-3149 > URL: https://issues.apache.org/jira/browse/FOP-3149 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, test.fo > > > fop test.fo -c fop.xconf out.pdf > Output font size should match input pdf -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3149) Don't merge fonts when ascent is different
[ https://issues.apache.org/jira/browse/FOP-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3149: --- Attachment: fop.xconf test.fo > Don't merge fonts when ascent is different > -- > > Key: FOP-3149 > URL: https://issues.apache.org/jira/browse/FOP-3149 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, test.fo > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3149) Don't merge fonts when ascent is different
Simon Steiner created FOP-3149: -- Summary: Don't merge fonts when ascent is different Key: FOP-3149 URL: https://issues.apache.org/jira/browse/FOP-3149 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner Attachments: fop.xconf, test.fo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-3148) NoSuchElementException when using font with no family name
[ https://issues.apache.org/jira/browse/FOP-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3148. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop/commit/7f01c67a96493fc5d6275a25414dd0841a2617b9 > NoSuchElementException when using font with no family name > -- > > Key: FOP-3148 > URL: https://issues.apache.org/jira/browse/FOP-3148 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > Attachments: fop.xconf, simple.fo, test2.svg > > > java.util.NoSuchElementException > at java.util.HashMap$HashIterator.nextNode(HashMap.java:1447) > at java.util.HashMap$KeyIterator.next(HashMap.java:1469) > at > java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1042) > at > org.apache.fop.svg.font.FOPFontFamilyResolverImpl.getFamilyThatCanDisplay(FOPFontFamilyResolverImpl.java:71) > fop simple.fo -c fop.xconf out.pdf -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3148) NoSuchElementException when using font with no family name
[ https://issues.apache.org/jira/browse/FOP-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3148: --- Description: java.util.NoSuchElementException at java.util.HashMap$HashIterator.nextNode(HashMap.java:1447) at java.util.HashMap$KeyIterator.next(HashMap.java:1469) at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1042) at org.apache.fop.svg.font.FOPFontFamilyResolverImpl.getFamilyThatCanDisplay(FOPFontFamilyResolverImpl.java:71) fop simple.fo -c fop.xconf out.pdf was: java.util.NoSuchElementException at java.util.HashMap$HashIterator.nextNode(HashMap.java:1447) at java.util.HashMap$KeyIterator.next(HashMap.java:1469) at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1042) at org.apache.fop.svg.font.FOPFontFamilyResolverImpl.getFamilyThatCanDisplay(FOPFontFamilyResolverImpl.java:71) > NoSuchElementException when using font with no family name > -- > > Key: FOP-3148 > URL: https://issues.apache.org/jira/browse/FOP-3148 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, simple.fo, test2.svg > > > java.util.NoSuchElementException > at java.util.HashMap$HashIterator.nextNode(HashMap.java:1447) > at java.util.HashMap$KeyIterator.next(HashMap.java:1469) > at > java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1042) > at > org.apache.fop.svg.font.FOPFontFamilyResolverImpl.getFamilyThatCanDisplay(FOPFontFamilyResolverImpl.java:71) > fop simple.fo -c fop.xconf out.pdf -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3148) GI-7244: NoSuchElementException when using font with no family name
Simon Steiner created FOP-3148: -- Summary: GI-7244: NoSuchElementException when using font with no family name Key: FOP-3148 URL: https://issues.apache.org/jira/browse/FOP-3148 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner Attachments: fop.xconf, simple.fo, test2.svg java.util.NoSuchElementException at java.util.HashMap$HashIterator.nextNode(HashMap.java:1447) at java.util.HashMap$KeyIterator.next(HashMap.java:1469) at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1042) at org.apache.fop.svg.font.FOPFontFamilyResolverImpl.getFamilyThatCanDisplay(FOPFontFamilyResolverImpl.java:71) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3148) NoSuchElementException when using font with no family name
[ https://issues.apache.org/jira/browse/FOP-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3148: --- Attachment: fop.xconf simple.fo test2.svg > NoSuchElementException when using font with no family name > -- > > Key: FOP-3148 > URL: https://issues.apache.org/jira/browse/FOP-3148 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, simple.fo, test2.svg > > > java.util.NoSuchElementException > at java.util.HashMap$HashIterator.nextNode(HashMap.java:1447) > at java.util.HashMap$KeyIterator.next(HashMap.java:1469) > at > java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1042) > at > org.apache.fop.svg.font.FOPFontFamilyResolverImpl.getFamilyThatCanDisplay(FOPFontFamilyResolverImpl.java:71) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3148) NoSuchElementException when using font with no family name
[ https://issues.apache.org/jira/browse/FOP-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3148: --- Summary: NoSuchElementException when using font with no family name (was: GI-7244: NoSuchElementException when using font with no family name) > NoSuchElementException when using font with no family name > -- > > Key: FOP-3148 > URL: https://issues.apache.org/jira/browse/FOP-3148 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, simple.fo, test2.svg > > > java.util.NoSuchElementException > at java.util.HashMap$HashIterator.nextNode(HashMap.java:1447) > at java.util.HashMap$KeyIterator.next(HashMap.java:1469) > at > java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1042) > at > org.apache.fop.svg.font.FOPFontFamilyResolverImpl.getFamilyThatCanDisplay(FOPFontFamilyResolverImpl.java:71) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-3146) FOP 2.9 shows a version of SVN instead of 2.9
[ https://issues.apache.org/jira/browse/FOP-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3146. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop/commit/fa89ae7b7a349d7f015b6eeb650a839979a8eed0 > FOP 2.9 shows a version of SVN instead of 2.9 > - > > Key: FOP-3146 > URL: https://issues.apache.org/jira/browse/FOP-3146 > Project: FOP > Issue Type: Bug >Affects Versions: 2.9 >Reporter: Simcha Gralla >Assignee: Simon Steiner >Priority: Trivial > Fix For: main > > > With the latest set of binaries, "fop -version" for 2.9 returns "FOP Version > SVN" instead of "FOP Version 2.9". The same is being returned in the PDF > properties. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FOP-3146) FOP 2.9 shows a version of SVN instead of 2.9
[ https://issues.apache.org/jira/browse/FOP-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner reassigned FOP-3146: -- Assignee: Simon Steiner > FOP 2.9 shows a version of SVN instead of 2.9 > - > > Key: FOP-3146 > URL: https://issues.apache.org/jira/browse/FOP-3146 > Project: FOP > Issue Type: Bug >Affects Versions: 2.9 >Reporter: Simcha Gralla >Assignee: Simon Steiner >Priority: Trivial > > With the latest set of binaries, "fop -version" for 2.9 returns "FOP Version > SVN" instead of "FOP Version 2.9". The same is being returned in the PDF > properties. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3145) [PATCH] Fix creating empty GAD fields when embedding GOCA objects greater than 8192 bytes in size in AFP
[ https://issues.apache.org/jira/browse/FOP-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3145: --- Fix Version/s: (was: 2.8) > [PATCH] Fix creating empty GAD fields when embedding GOCA objects greater > than 8192 bytes in size in AFP > > > Key: FOP-3145 > URL: https://issues.apache.org/jira/browse/FOP-3145 > Project: FOP > Issue Type: Bug >Affects Versions: 2.8 >Reporter: Christopher Thumberger >Priority: Minor > Attachments: EmptyGADFields.patch, image-2023-08-23-16-51-11-519.png, > image-2023-08-23-16-53-06-714.png > > > When a GraphicsData object would exceed 8200 bytes in size, instead of moving > the last area of GOCA data to a new GraphicsData and continuing from there, > FOP currently moves the data into a new GraphicsData object, leaving the old > one empty. This is technically not a violation of MODCA spec, but has caused > crashes in AFP viewer software. My patch prevents GAD fields ever exceedining > 8200 bytes and prevents GOCA instructions being cut up between segments. > Below is an example of the current behaviour as of FOP 2.8 visualized with > AFPExplorer and my fixed version with the same input data. > !image-2023-08-23-16-51-11-519.png! > !image-2023-08-23-16-53-06-714.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FOP-3098) [PATCH] Nullpointer Exception in LMiter.next depending on text
[
https://issues.apache.org/jira/browse/FOP-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17756894#comment-17756894
]
Simon Steiner commented on FOP-3098:
https://github.com/apache/xmlgraphics-fop/commit/03a69c051cbb867d3d037ed95c2344ab996b5dc4
> [PATCH] Nullpointer Exception in LMiter.next depending on text
> --
>
> Key: FOP-3098
> URL: https://issues.apache.org/jira/browse/FOP-3098
> Project: FOP
> Issue Type: Bug
> Components: fo/unqualified
>Affects Versions: 2.7
> Environment: Windows 10
>Reporter: Michael Heitkamp
>Assignee: Chris Bowditch
>Priority: Major
> Fix For: 2.9
>
> Attachments: Post-FOP-3098-NPE-Bugfix.diff, patch.txt,
> patch_cached.txt, stacktrace.txt, x-fop-error.xml, x-fop-error.xsl
>
>
> Doing a FOP translation with the given XSL and XML input files lead to a
> Nullpointer Exception.
> If the text block is shortened by one character ("dataX" -> "data") then the
> translation succeeds.
> If the text block is replaced by "lore ipsum" of the same length then the
> translation succeeds also.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FOP-3088) [PATCH] Jar packaging duplicates classes on classpath
[
https://issues.apache.org/jira/browse/FOP-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner resolved FOP-3088.
Fix Version/s: main
Resolution: Fixed
https://github.com/apache/xmlgraphics-fop/commit/64585e49741c561e313dd751458d8660dca8f708
> [PATCH] Jar packaging duplicates classes on classpath
> -
>
> Key: FOP-3088
> URL: https://issues.apache.org/jira/browse/FOP-3088
> Project: FOP
> Issue Type: Bug
>Reporter: Skip de Groot
>Assignee: Simon Steiner
>Priority: Major
> Fix For: main
>
> Attachments: 3088-patch.diff
>
>
> I have a gradle project where we import apache fop with the following:
> {code:java}
> implementation("org.apache.xmlgraphics:fop:2.6") {code}
> Which results in the following dependencies being loaded on the classpath (I
> have removed the sub dependencies for simplicity)
> {code:java}
> org.apache.xmlgraphics:fop -> 2.6
> +--- org.apache.xmlgraphics:fop-util:2.6
> +--- org.apache.xmlgraphics:fop-events:2.6
> \--- org.apache.xmlgraphics:fop-core:2.6 {code}
> So far so good and everything works most of the time. I suspect any maven
> project would import in the same way.
> However, most classes are duplicated in fop-2.6.jar and their respective sub
> module. For instance, the org.apache.fop.apps.FOUserAgent class is packaged
> both in fop and fop-core.
> All classes from the fop-events module in org.apache.fop.events package are
> also duplicated, but not from the org.apache.fop.tools package from the
> fop-events module (For instance org.apache.fop.tools.EventProducerCollector),
> making this also inconsistent somehow.
> Luckily both implementations seem the same but it is bad practice to have
> duplicate classes on the classpath, and package sizes are also doubled.
>
> Depending on the implementation choice I would either expect a fatty jar with
> all the classes packaged which does not import anything or an somewhat empty
> root fop jar with all classes imported by the sub modules. As it stands now
> it seems to be a combination of both and not a completely consistant one
> either.
> Which one is the prefered solution of this project?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FOP-3088) [PATCH] Jar packaging duplicates classes on classpath
[
https://issues.apache.org/jira/browse/FOP-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner reassigned FOP-3088:
--
Assignee: Simon Steiner
> [PATCH] Jar packaging duplicates classes on classpath
> -
>
> Key: FOP-3088
> URL: https://issues.apache.org/jira/browse/FOP-3088
> Project: FOP
> Issue Type: Bug
>Reporter: Skip de Groot
>Assignee: Simon Steiner
>Priority: Major
> Attachments: 3088-patch.diff
>
>
> I have a gradle project where we import apache fop with the following:
> {code:java}
> implementation("org.apache.xmlgraphics:fop:2.6") {code}
> Which results in the following dependencies being loaded on the classpath (I
> have removed the sub dependencies for simplicity)
> {code:java}
> org.apache.xmlgraphics:fop -> 2.6
> +--- org.apache.xmlgraphics:fop-util:2.6
> +--- org.apache.xmlgraphics:fop-events:2.6
> \--- org.apache.xmlgraphics:fop-core:2.6 {code}
> So far so good and everything works most of the time. I suspect any maven
> project would import in the same way.
> However, most classes are duplicated in fop-2.6.jar and their respective sub
> module. For instance, the org.apache.fop.apps.FOUserAgent class is packaged
> both in fop and fop-core.
> All classes from the fop-events module in org.apache.fop.events package are
> also duplicated, but not from the org.apache.fop.tools package from the
> fop-events module (For instance org.apache.fop.tools.EventProducerCollector),
> making this also inconsistent somehow.
> Luckily both implementations seem the same but it is bad practice to have
> duplicate classes on the classpath, and package sizes are also doubled.
>
> Depending on the implementation choice I would either expect a fatty jar with
> all the classes packaged which does not import anything or an somewhat empty
> root fop jar with all classes imported by the sub modules. As it stands now
> it seems to be a combination of both and not a completely consistant one
> either.
> Which one is the prefered solution of this project?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FOP-3142) Fatal error when compiling large xsl templates
[
https://issues.apache.org/jira/browse/FOP-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750352#comment-17750352
]
Simon Steiner commented on FOP-3142:
Bundling xalan mean we have to make a new fop release for every xalan security
fix
> Fatal error when compiling large xsl templates
> --
>
> Key: FOP-3142
> URL: https://issues.apache.org/jira/browse/FOP-3142
> Project: FOP
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Huy Ho
>Priority: Critical
>
> After we updated from FOP 2.6 to the latest FOP 2.8 version, our application
> is running into the following error when compiling our stylesheets (stack
> trace below). To get around this issue, we downloaded the latest xalan-j
> 2.7.3 library from [https://xalan.apache.org/xalan-j/index.html] and drop
> them in the fop/lib directory.
>
> {{java.lang.RuntimeException: XPATH_LIMIT}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.Parser.parseTopLevel(Parser.java:1165)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.Parser.parseExpression(Parser.java:1112)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.VariableBase.parseContents(VariableBase.java:250)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.Param.parseContents(Param.java:106)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.Stylesheet.parseOwnChildren(Stylesheet.java:587)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.Stylesheet.parseContents(Stylesheet.java:559)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.Import.parseContents(Import.java:132)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.Stylesheet.parseOwnChildren(Stylesheet.java:597)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.Stylesheet.parseContents(Stylesheet.java:559)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.Parser.createAST(Parser.java:398)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.XSLTC.compile(XSLTC.java:496)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.XSLTC.compile(XSLTC.java:576)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:1018)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:817)}}
> {{ at
> org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:274)}}
> {{ at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:116)}}
> {{ at org.apache.fop.cli.Main.startFOP(Main.java:183)}}
> {{ at org.apache.fop.cli.Main.main(Main.java:214)}}
>
> {{ERROR: 'JAXP0801003: the compiler encountered XPath expressions with an
> accumulated '10,001' operators that exceeds the '10,000' limit set by
> 'FEATURE_SECURE_PROCESSING'.'}}
> {{FATAL ERROR: 'JAXP0801003: the compiler encountered XPath expressions with
> an accumulated '10,001' operators that exceeds the '10,000' limit set by
> 'FEATURE_SECURE_PROCESSING'.'}}
> {{[ERROR] FOP - Exception javax.xml.transform.TransformerConfigurationException: JAXP0801003: the
> compiler encountered XPath expressions with an accumulated '10,001' operators
> that exceeds the '10,000' limit set by 'FEATURE_SECURE_PROCESSING'.}}
> {{javax.xml.transform.TransformerConfigurationException: JAXP0801003: the
> compiler encountered XPath expressions with an accumulated '10,001' operators
> that exceeds the '10,000' limit set by
> 'FEATURE_SECURE_PROCESSING'.>org.apache.fop.apps.FOPException:
> javax.xml.transform.TransformerConfigurationException: JAXP0801003: the
> compiler encountered XPath expressions with an accumulated '10,001' operators
> that exceeds the '10,000' limit set by 'FEATURE_SECURE_PROCESSING'.}}
> {{javax.xml.transform.TransformerConfigurationException: JAXP0801003: the
> compiler encountered XPath expressions with an accumulated '10,001' operators
> that exceeds the '10,000' limit set by 'FEATURE_SECURE_PROCESSING'.}}
> {{ at
> org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:296)}}
> {{ at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:116)}}
> {{ at org.apache.fop.cli.Main.startFOP(Main.java:183)}}
> {{ at org.apache.fop.cli.Main.main(Main.java:214)}}
> {{Caused by: javax.xml.transform.TransformerConfigurationException:
> JAXP0801003: the compiler encountered XPath expressions with an accumulated
> '10,001' operators that exceeds the '10,000' limit set by
> 'FEATURE_SECURE_PROCESSING'.}}
> {{ at
>
[jira] [Commented] (FOP-3142) Fatal error when compiling large xsl templates
[
https://issues.apache.org/jira/browse/FOP-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17750117#comment-17750117
]
Simon Steiner commented on FOP-3142:
We are using xalan from jdk, what java version are you using?
> Fatal error when compiling large xsl templates
> --
>
> Key: FOP-3142
> URL: https://issues.apache.org/jira/browse/FOP-3142
> Project: FOP
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Huy Ho
>Priority: Critical
>
> After we updated from FOP 2.6 to the latest FOP 2.8 version, our application
> is running into the following error when compiling our stylesheets (stack
> trace below). To get around this issue, we downloaded the latest xalan-j
> 2.7.3 library from [https://xalan.apache.org/xalan-j/index.html] and drop
> them in the fop/lib directory.
>
> {{java.lang.RuntimeException: XPATH_LIMIT}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.Parser.parseTopLevel(Parser.java:1165)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.Parser.parseExpression(Parser.java:1112)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.VariableBase.parseContents(VariableBase.java:250)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.Param.parseContents(Param.java:106)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.Stylesheet.parseOwnChildren(Stylesheet.java:587)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.Stylesheet.parseContents(Stylesheet.java:559)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.Import.parseContents(Import.java:132)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.Stylesheet.parseOwnChildren(Stylesheet.java:597)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.Stylesheet.parseContents(Stylesheet.java:559)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.Parser.createAST(Parser.java:398)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.XSLTC.compile(XSLTC.java:496)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.compiler.XSLTC.compile(XSLTC.java:576)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:1018)}}
> {{ at
> java.xml/com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:817)}}
> {{ at
> org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:274)}}
> {{ at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:116)}}
> {{ at org.apache.fop.cli.Main.startFOP(Main.java:183)}}
> {{ at org.apache.fop.cli.Main.main(Main.java:214)}}
>
> {{ERROR: 'JAXP0801003: the compiler encountered XPath expressions with an
> accumulated '10,001' operators that exceeds the '10,000' limit set by
> 'FEATURE_SECURE_PROCESSING'.'}}
> {{FATAL ERROR: 'JAXP0801003: the compiler encountered XPath expressions with
> an accumulated '10,001' operators that exceeds the '10,000' limit set by
> 'FEATURE_SECURE_PROCESSING'.'}}
> {{[ERROR] FOP - Exception javax.xml.transform.TransformerConfigurationException: JAXP0801003: the
> compiler encountered XPath expressions with an accumulated '10,001' operators
> that exceeds the '10,000' limit set by 'FEATURE_SECURE_PROCESSING'.}}
> {{javax.xml.transform.TransformerConfigurationException: JAXP0801003: the
> compiler encountered XPath expressions with an accumulated '10,001' operators
> that exceeds the '10,000' limit set by
> 'FEATURE_SECURE_PROCESSING'.>org.apache.fop.apps.FOPException:
> javax.xml.transform.TransformerConfigurationException: JAXP0801003: the
> compiler encountered XPath expressions with an accumulated '10,001' operators
> that exceeds the '10,000' limit set by 'FEATURE_SECURE_PROCESSING'.}}
> {{javax.xml.transform.TransformerConfigurationException: JAXP0801003: the
> compiler encountered XPath expressions with an accumulated '10,001' operators
> that exceeds the '10,000' limit set by 'FEATURE_SECURE_PROCESSING'.}}
> {{ at
> org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:296)}}
> {{ at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:116)}}
> {{ at org.apache.fop.cli.Main.startFOP(Main.java:183)}}
> {{ at org.apache.fop.cli.Main.main(Main.java:214)}}
> {{Caused by: javax.xml.transform.TransformerConfigurationException:
> JAXP0801003: the compiler encountered XPath expressions with an accumulated
> '10,001' operators that exceeds the '10,000' limit set by
> 'FEATURE_SECURE_PROCESSING'.}}
> {{ at
>
[jira] [Updated] (FOP-2920) [PATCH] Surrogate pair edge-case causes java.lang.ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/FOP-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner updated FOP-2920:
---
Attachment: fop.xconf
> [PATCH] Surrogate pair edge-case causes
> java.lang.ArrayIndexOutOfBoundsException
>
>
> Key: FOP-2920
> URL: https://issues.apache.org/jira/browse/FOP-2920
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.5
> Environment: macOS Mojave
> java version "1.8.0_192-ea"
> Java(TM) SE Runtime Environment (build 1.8.0_192-ea-b04)
> Java HotSpot(TM) 64-Bit Server VM (build 25.192-b04, mixed mode)
>Reporter: Kelly H Wilkerson
>Assignee: Simon Steiner
>Priority: Minor
> Fix For: main
>
> Attachments: 2920.patch, TwitterColorEmoji-SVGinOT.ttf, diff.txt,
> fail.xml, fop.xconf, s6.patch, twe_template.fo, twe_userconfig.xml
>
>
> fop-core/src/main/java/org/apache/fop/pdf/PDFToUnicodeCMap.java
> writeBFCharEntries runs through the codepoint entries in sections of 100 at a
> time. It looks like there's an edge case here where the last entry in the
> section is a surrogate pair.
>
> Here's my steps to reproduce from the latest trunk:
> {{java -cp
> fop/target/fop-2.5.0-SNAPSHOT.jar:fop/lib/commons-logging-1.0.4.jar:fop/lib/commons-io-1.3.1.jar:fop/lib/xmlgraphics-commons-svn-trunk.jar
> org.apache.fop.fonts.apps.TTFReader TwitterColorEmoji-SVGinOT.ttf twe.xml}}
> {{java -cp
> fop/target/fop-2.5.0-SNAPSHOT.jar:fop/lib/commons-logging-1.0.4.jar:fop/lib/commons-io-1.3.1.jar:fop/lib/xmlgraphics-commons-svn-trunk.jar:fop/lib/batik-all-1.11.0-SNAPSHOT.jar
> org.apache.fop.cli.Main -c twe_userconfig.xml -xsl twe_template.fo -xml
> fail.xml -pdf fail.pdf}}
>
> Here's the temporary way I resolved it for my own build:
>
> index ee773dcec..37c21803e 100644
> --- a/fop-core/src/main/java/org/apache/fop/pdf/PDFToUnicodeCMap.java
> +++ b/fop-core/src/main/java/org/apache/fop/pdf/PDFToUnicodeCMap.java
> @@ -128,6 +128,18 @@ public class PDFToUnicodeCMap extends PDFCMap {
> while (partOfRange(charArray, charIndex)) {
> charIndex++;
> }
> /*
> * If this entry is going to overflow the entriesThisSection
> * array, then don't use it. This happens if there are
> * non-pair entries in the table mixed with pair entries.
> */
> if (Character.codePointAt(charArray, charIndex) > 0x
> && i+1 >= entriesThisSection) {
> entriesThisSection--;
> break;
> }
> writer.write("<" + padCharIndex(charIndex) + "> ");
> if (Character.codePointAt(charArray, charIndex) > 0x) {
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FOP-2903) [PATCH] Do not delete files on invocation with syntax errors in command line
[
https://issues.apache.org/jira/browse/FOP-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner resolved FOP-2903.
Fix Version/s: main
Resolution: Fixed
https://github.com/apache/xmlgraphics-fop/commit/a731bf3ab28f7f7760421e5f9b90916bc3cf627c
> [PATCH] Do not delete files on invocation with syntax errors in command line
>
>
> Key: FOP-2903
> URL: https://issues.apache.org/jira/browse/FOP-2903
> Project: FOP
> Issue Type: Bug
> Components: unqualified
>Affects Versions: 2.3
> Environment: Linux RHEL 7, FOP installed from source
>Reporter: Mathias Weiersmueller
>Assignee: Simon Steiner
>Priority: Trivial
> Fix For: main
>
> Attachments: p5.patch
>
>
> When invoking FOP from the command line with an error, fop deletes files. I
> expect FOP to touch nothing upon an error.
> Example:
> {{fop -xml ./my.xml my.xsl -pdf result.pdf}}
> above command throws as expected an error because the -xsl flag is missing in
> front of the XSL file name:
> Jan 15, 2020 8:56:03 AM org.apache.fop.cli.Main startFOP
> SEVERE: Exception
> org.apache.fop.apps.FOPException: you can only set one output method
> But the file my.xsl is gone (deleted) afterwards. The file should not get
> deleted upon an error in the command line.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FOP-2903) [PATCH] Do not delete files on invocation with syntax errors in command line
[
https://issues.apache.org/jira/browse/FOP-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner reassigned FOP-2903:
--
Assignee: Simon Steiner
> [PATCH] Do not delete files on invocation with syntax errors in command line
>
>
> Key: FOP-2903
> URL: https://issues.apache.org/jira/browse/FOP-2903
> Project: FOP
> Issue Type: Bug
> Components: unqualified
>Affects Versions: 2.3
> Environment: Linux RHEL 7, FOP installed from source
>Reporter: Mathias Weiersmueller
>Assignee: Simon Steiner
>Priority: Trivial
> Attachments: p5.patch
>
>
> When invoking FOP from the command line with an error, fop deletes files. I
> expect FOP to touch nothing upon an error.
> Example:
> {{fop -xml ./my.xml my.xsl -pdf result.pdf}}
> above command throws as expected an error because the -xsl flag is missing in
> front of the XSL file name:
> Jan 15, 2020 8:56:03 AM org.apache.fop.cli.Main startFOP
> SEVERE: Exception
> org.apache.fop.apps.FOPException: you can only set one output method
> But the file my.xsl is gone (deleted) afterwards. The file should not get
> deleted upon an error in the command line.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FOP-3140) Merge form fields in external PDFs
[ https://issues.apache.org/jira/browse/FOP-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3140. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop-pdf-images/commit/ed4a9422e67fe41791a7728ea857a38598d88aa2 https://github.com/apache/xmlgraphics-fop/commit/3dd36e9bb26df83fa8677425f7f16e1d53001409 > Merge form fields in external PDFs > -- > > Key: FOP-3140 > URL: https://issues.apache.org/jira/browse/FOP-3140 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > Attachments: fop.xconf, simple1.pdf, simple2.pdf, test.fo > > > fop test.fo -c fop.xconf out.pdf > Open output in Acrobat Pro, click edit forms button, form fields names should > match the input pdfs -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3140) Merge form fields in external PDFs
[ https://issues.apache.org/jira/browse/FOP-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3140: --- Description: fop test.fo -c fop.xconf out.pdf Open output in Acrobat Pro, click edit forms button, form fields names should match the input pdfs > Merge form fields in external PDFs > -- > > Key: FOP-3140 > URL: https://issues.apache.org/jira/browse/FOP-3140 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, simple1.pdf, simple2.pdf, test.fo > > > fop test.fo -c fop.xconf out.pdf > Open output in Acrobat Pro, click edit forms button, form fields names should > match the input pdfs -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3140) Merge form fields in external PDFs
[ https://issues.apache.org/jira/browse/FOP-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3140: --- Attachment: fop.xconf simple1.pdf simple2.pdf test.fo > Merge form fields in external PDFs > -- > > Key: FOP-3140 > URL: https://issues.apache.org/jira/browse/FOP-3140 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, simple1.pdf, simple2.pdf, test.fo > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3140) Merge form fields in external PDFs
Simon Steiner created FOP-3140: -- Summary: Merge form fields in external PDFs Key: FOP-3140 URL: https://issues.apache.org/jira/browse/FOP-3140 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner Attachments: fop.xconf, simple1.pdf, simple2.pdf, test.fo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-2985) [PATCH] SVG Images inherit font configuration from sibling objects.
[ https://issues.apache.org/jira/browse/FOP-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-2985. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop/commit/05f8a2c9d2084b29b7ddf49a25d6a8e028243b7c > [PATCH] SVG Images inherit font configuration from sibling objects. > --- > > Key: FOP-2985 > URL: https://issues.apache.org/jira/browse/FOP-2985 > Project: FOP > Issue Type: Bug > Components: image/svg >Reporter: Juan >Assignee: Simon Steiner >Priority: Minor > Fix For: main > > Attachments: SVG-letter-spacing.patch, input.fo, p5.patch, sample.svg > > > Given the sample [^input.fo] (adjust the path to sample.svg), the letter > spacing of an inline element in a previous block is being applied also to an > external-graphic element on a different block. > The letter spacing property in the inline element should not affect the > external-graphic in a different block. > Additionally, setting letter-spacing on the external-graphic or it's parent > block has no effect and the content still used the letter-spacing of the > previous inline text. > > The given patch [^SVG-letter-spacing.patch] does fix the issue with > letter-spacing, altough *it might need a more generic approach*. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FOP-2985) [PATCH] SVG Images inherit font configuration from sibling objects.
[ https://issues.apache.org/jira/browse/FOP-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner reassigned FOP-2985: -- Assignee: Simon Steiner > [PATCH] SVG Images inherit font configuration from sibling objects. > --- > > Key: FOP-2985 > URL: https://issues.apache.org/jira/browse/FOP-2985 > Project: FOP > Issue Type: Bug > Components: image/svg >Reporter: Juan >Assignee: Simon Steiner >Priority: Minor > Attachments: SVG-letter-spacing.patch, input.fo, p5.patch, sample.svg > > > Given the sample [^input.fo] (adjust the path to sample.svg), the letter > spacing of an inline element in a previous block is being applied also to an > external-graphic element on a different block. > The letter spacing property in the inline element should not affect the > external-graphic in a different block. > Additionally, setting letter-spacing on the external-graphic or it's parent > block has no effect and the content still used the letter-spacing of the > previous inline text. > > The given patch [^SVG-letter-spacing.patch] does fix the issue with > letter-spacing, altough *it might need a more generic approach*. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-3139) Add support for font-selection-strategy=character-by-character
[ https://issues.apache.org/jira/browse/FOP-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3139. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop/commit/b16022ece329197f72f47943085d45b56e26806e > Add support for font-selection-strategy=character-by-character > -- > > Key: FOP-3139 > URL: https://issues.apache.org/jira/browse/FOP-3139 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > Attachments: test2.fo > > > fop test.fo out.pdf > All glyphs should map to a font -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3139) Add support for font-selection-strategy=character-by-character
[ https://issues.apache.org/jira/browse/FOP-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3139: --- Description: fop test.fo out.pdf All glyphs should map to a font > Add support for font-selection-strategy=character-by-character > -- > > Key: FOP-3139 > URL: https://issues.apache.org/jira/browse/FOP-3139 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test2.fo > > > fop test.fo out.pdf > All glyphs should map to a font -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3139) Add support for font-selection-strategy=character-by-character
[ https://issues.apache.org/jira/browse/FOP-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3139: --- Attachment: test2.fo > Add support for font-selection-strategy=character-by-character > -- > > Key: FOP-3139 > URL: https://issues.apache.org/jira/browse/FOP-3139 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test2.fo > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3139) Add support for font-selection-strategy=character-by-character
Simon Steiner created FOP-3139: -- Summary: Add support for font-selection-strategy=character-by-character Key: FOP-3139 URL: https://issues.apache.org/jira/browse/FOP-3139 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-3138) NPE when no annotation field in external PDF
[ https://issues.apache.org/jira/browse/FOP-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3138. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop-pdf-images/commit/028c6b6f3e64520ec16841c346c3ee55ae81264f > NPE when no annotation field in external PDF > > > Key: FOP-3138 > URL: https://issues.apache.org/jira/browse/FOP-3138 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > Attachments: helloworld_annotation.pdf, test.fo > > > fop test.fo out.pdf > Caused by: java.lang.NullPointerException > at > org.apache.fop.render.pdf.pdfbox.PDFBoxAdapter.getField(PDFBoxAdapter.java:638) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3138) NPE when no annotation field in external PDF
Simon Steiner created FOP-3138: -- Summary: NPE when no annotation field in external PDF Key: FOP-3138 URL: https://issues.apache.org/jira/browse/FOP-3138 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner Attachments: helloworld_annotation.pdf, test.fo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3138) NPE when no annotation field in external PDF
[ https://issues.apache.org/jira/browse/FOP-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3138: --- Attachment: helloworld_annotation.pdf test.fo > NPE when no annotation field in external PDF > > > Key: FOP-3138 > URL: https://issues.apache.org/jira/browse/FOP-3138 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: helloworld_annotation.pdf, test.fo > > > fop test.fo out.pdf > Caused by: java.lang.NullPointerException > at > org.apache.fop.render.pdf.pdfbox.PDFBoxAdapter.getField(PDFBoxAdapter.java:638) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3138) NPE when no annotation field in external PDF
[ https://issues.apache.org/jira/browse/FOP-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3138: --- Description: fop test.fo out.pdf Caused by: java.lang.NullPointerException at org.apache.fop.render.pdf.pdfbox.PDFBoxAdapter.getField(PDFBoxAdapter.java:638) > NPE when no annotation field in external PDF > > > Key: FOP-3138 > URL: https://issues.apache.org/jira/browse/FOP-3138 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: helloworld_annotation.pdf, test.fo > > > fop test.fo out.pdf > Caused by: java.lang.NullPointerException > at > org.apache.fop.render.pdf.pdfbox.PDFBoxAdapter.getField(PDFBoxAdapter.java:638) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-2986) NUllPointer external-graphic
[ https://issues.apache.org/jira/browse/FOP-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-2986. Resolution: Not A Problem > NUllPointer external-graphic > > > Key: FOP-2986 > URL: https://issues.apache.org/jira/browse/FOP-2986 > Project: FOP > Issue Type: Bug >Affects Versions: 2.6 > Environment: fop 2.5 > jdk 8 > linux manjaro > apache tomcat 7.0.69 >Reporter: Ramon Molossi >Priority: Major > Attachments: teste.xml, teste.xslt > > > Downloaded sources from apache site, compiled by myself, trying to adjust > fop-servlet to work togheter with Oracle Apex. > > Trying to use the default FopServlet(just changed from doGet to doPost), > submitted xsl and xml, when I add a simple external graphic like this: > > > > I get this error: > java.lang.NullPointerException > java.io.FilterInputStream.markSupported(FilterInputStream.java:243) > org.apache.xmlgraphics.image.loader.util.ImageUtil.decorateMarkSupported(ImageUtil.java:213) > > org.apache.xmlgraphics.image.loader.util.ImageUtil.autoDecorateInputStream(ImageUtil.java:228) > > org.apache.xmlgraphics.image.loader.impl.AbstractImageSessionContext.createImageSource(AbstractImageSessionContext.java:378) > > org.apache.xmlgraphics.image.loader.impl.AbstractImageSessionContext.access$100(AbstractImageSessionContext.java:54) > > org.apache.xmlgraphics.image.loader.impl.AbstractImageSessionContext$UnrestrictedFallbackResolver.createSource(AbstractImageSessionContext.java:369) > > org.apache.xmlgraphics.image.loader.impl.AbstractImageSessionContext.newSource(AbstractImageSessionContext.java:95) > > org.apache.xmlgraphics.image.loader.impl.AbstractImageSessionContext.needSource(AbstractImageSessionContext.java:196) > > org.apache.xmlgraphics.image.loader.cache.ImageCache.needImageInfo(ImageCache.java:122) > > org.apache.xmlgraphics.image.loader.ImageManager.getImageInfo(ImageManager.java:123) > org.apache.fop.fo.flow.ExternalGraphic.bind(ExternalGraphic.java:81) > org.apache.fop.fo.FObj.processNode(FObj.java:131) > org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:293) > org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:179) > com.sun.org.apache.xml.internal.serializer.ToXMLSAXHandler.closeStartTag(ToXMLSAXHandler.java:208) > > com.sun.org.apache.xml.internal.serializer.ToSAXHandler.flushPending(ToSAXHandler.java:281) > > com.sun.org.apache.xml.internal.serializer.ToXMLSAXHandler.endElement(ToXMLSAXHandler.java:247) > > com.sun.org.apache.xml.internal.serializer.ToXMLSAXHandler.endElement(ToXMLSAXHandler.java:559) > teste.template$dot$0() teste.applyTemplates() teste.transform() > com.sun.org.apache.xalan.internal.xsltc.runtime.AbstractTranslet.transform(AbstractTranslet.java:620) > > com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:730) > > com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:343) > org.apache.fop.servlet.FopServlet.render(FopServlet.java:269) > org.apache.fop.servlet.FopServlet.renderXML(FopServlet.java:236) > org.apache.fop.servlet.FopServlet.doPost(FopServlet.java:142) > javax.servlet.http.HttpServlet.service(HttpServlet.java:650) > javax.servlet.http.HttpServlet.service(HttpServlet.java:731) > org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) > > > Tried to downgrade the xmlgraphics-commons to 2.3, got same error. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-3042) [PATCH] SVG text containing certain glyphs isn't rendered
[ https://issues.apache.org/jira/browse/FOP-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3042. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop/commit/6f6e58d7b89b04847f37ad887aa2b7235c2b484f > [PATCH] SVG text containing certain glyphs isn't rendered > - > > Key: FOP-3042 > URL: https://issues.apache.org/jira/browse/FOP-3042 > Project: FOP > Issue Type: Bug > Components: foreign/svg >Affects Versions: 2.3, 2.4, 2.6 >Reporter: Per Cederberg >Assignee: Simon Steiner >Priority: Major > Fix For: main > > Attachments: CenturyGothicStd.otf, fopconfig.xml, output-fop2.2.pdf, > output-fop2.3.pdf, p4.patch, test.xml > > > When rendering an XSL-FO containing an inline SVG with a custom font (Century > Gothic), text is only displayed if it doesn't contain the "o" character > inside a word. > The provided "test.xml" file includes a minimal SVG image that shows this > behavior. Everything works correctly from FOP 1.x - 2.2. But starting with > FOP 2.3, some text lines might be omitted from the output. Typically lines > containing an "o" glyph inside a word. Might also be triggered by other > glyphs, as I haven't tested exhaustively with whole alphabet. > The attached "output-fop2.2.pdf" shows a correct rendering, whereas the > "output-fop2.3.pdf" shows rendering in 2.3, 2.4 and 2.6. > *Disclaimer:* This may actually be a bug in Apache Batik (1.10 and up), but > I'm currently unable to reproduce it using their command-line rasterizer tool. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FOP-3042) [PATCH] SVG text containing certain glyphs isn't rendered
[ https://issues.apache.org/jira/browse/FOP-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner reassigned FOP-3042: -- Assignee: Simon Steiner > [PATCH] SVG text containing certain glyphs isn't rendered > - > > Key: FOP-3042 > URL: https://issues.apache.org/jira/browse/FOP-3042 > Project: FOP > Issue Type: Bug > Components: foreign/svg >Affects Versions: 2.3, 2.4, 2.6 >Reporter: Per Cederberg >Assignee: Simon Steiner >Priority: Major > Attachments: CenturyGothicStd.otf, fopconfig.xml, output-fop2.2.pdf, > output-fop2.3.pdf, p4.patch, test.xml > > > When rendering an XSL-FO containing an inline SVG with a custom font (Century > Gothic), text is only displayed if it doesn't contain the "o" character > inside a word. > The provided "test.xml" file includes a minimal SVG image that shows this > behavior. Everything works correctly from FOP 1.x - 2.2. But starting with > FOP 2.3, some text lines might be omitted from the output. Typically lines > containing an "o" glyph inside a word. Might also be triggered by other > glyphs, as I haven't tested exhaustively with whole alphabet. > The attached "output-fop2.2.pdf" shows a correct rendering, whereas the > "output-fop2.3.pdf" shows rendering in 2.3, 2.4 and 2.6. > *Disclaimer:* This may actually be a bug in Apache Batik (1.10 and up), but > I'm currently unable to reproduce it using their command-line rasterizer tool. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-3136) FOP PDF Images - Some PDFs produce Error in Acrobat Reader
[
https://issues.apache.org/jira/browse/FOP-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner resolved FOP-3136.
Fix Version/s: main
Resolution: Fixed
https://github.com/apache/xmlgraphics-fop-pdf-images/commit/2d1c479e7a057109cb2b8509e606d3b8e346cb5a
> FOP PDF Images - Some PDFs produce Error in Acrobat Reader
> --
>
> Key: FOP-3136
> URL: https://issues.apache.org/jira/browse/FOP-3136
> Project: FOP
> Issue Type: Bug
>Reporter: Rafael Witak
>Assignee: Simon Steiner
>Priority: Major
> Fix For: main
>
> Attachments: p4.patch, p5.patch, resultA.pdf, resultB.pdf,
> resultC.pdf, softmask-min.pdf, softmask.pdf, sourceA.pdf, sourceB.pdf,
> sourceC.pdf
>
>
> Including some PDFs as external-document results in a PDF that produces an
> error in Acrobat Reader (but not in Chrome!). The error message reads
> "{*}There was an error processing a page. There was a problem reading this
> document{*} {*}(18).{*}" and after Ctrl-click on OK "{*}Expected a name
> object{*}{*}.{*}" is added. No page is visible.
> The issue can be traced back to FOP PDF Images and exists in all its versions
> >=2.6. Versions 2.5 and lower produce results that work.
> While the original PDFs do have some issues when checked with a tool like
> [pdfcpu|https://github.com/pdfcpu/pdfcpu/releases/tag/v0.4.0], others with
> similar issues don't produce the same error. The originals _can_ be opened by
> Adobe Reader without a problem.
> No ERROR or WARNING is logged. Searching on Google / Jira / the mailing list
> did not produce comparable problems.
> Due to the fact that I get the copyrighted PDFs as-is by the customer, I
> don't have much freedom in either changing them to work around the problems,
> or provide too many examples.
> Windows 10.0.19045 Build 19045
> Java 17
> FOP 2.8
> PDFBox 2.0.28
> PDF Images 2.8
> (Included are three example documents with their respective results.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FOP-3136) FOP PDF Images - Some PDFs produce Error in Acrobat Reader
[
https://issues.apache.org/jira/browse/FOP-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner reassigned FOP-3136:
--
Assignee: Simon Steiner
> FOP PDF Images - Some PDFs produce Error in Acrobat Reader
> --
>
> Key: FOP-3136
> URL: https://issues.apache.org/jira/browse/FOP-3136
> Project: FOP
> Issue Type: Bug
>Reporter: Rafael Witak
>Assignee: Simon Steiner
>Priority: Major
> Attachments: p4.patch, p5.patch, resultA.pdf, resultB.pdf,
> resultC.pdf, softmask-min.pdf, softmask.pdf, sourceA.pdf, sourceB.pdf,
> sourceC.pdf
>
>
> Including some PDFs as external-document results in a PDF that produces an
> error in Acrobat Reader (but not in Chrome!). The error message reads
> "{*}There was an error processing a page. There was a problem reading this
> document{*} {*}(18).{*}" and after Ctrl-click on OK "{*}Expected a name
> object{*}{*}.{*}" is added. No page is visible.
> The issue can be traced back to FOP PDF Images and exists in all its versions
> >=2.6. Versions 2.5 and lower produce results that work.
> While the original PDFs do have some issues when checked with a tool like
> [pdfcpu|https://github.com/pdfcpu/pdfcpu/releases/tag/v0.4.0], others with
> similar issues don't produce the same error. The originals _can_ be opened by
> Adobe Reader without a problem.
> No ERROR or WARNING is logged. Searching on Google / Jira / the mailing list
> did not produce comparable problems.
> Due to the fact that I get the copyrighted PDFs as-is by the customer, I
> don't have much freedom in either changing them to work around the problems,
> or provide too many examples.
> Windows 10.0.19045 Build 19045
> Java 17
> FOP 2.8
> PDFBox 2.0.28
> PDF Images 2.8
> (Included are three example documents with their respective results.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FOP-2920) [PATCH] Surrogate pair edge-case causes java.lang.ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/FOP-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner resolved FOP-2920.
Fix Version/s: main
Resolution: Fixed
https://github.com/apache/xmlgraphics-fop/commit/ae5f6dd6c3dcca0c56d06c634fe62da089d4e5e9
> [PATCH] Surrogate pair edge-case causes
> java.lang.ArrayIndexOutOfBoundsException
>
>
> Key: FOP-2920
> URL: https://issues.apache.org/jira/browse/FOP-2920
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.5
> Environment: macOS Mojave
> java version "1.8.0_192-ea"
> Java(TM) SE Runtime Environment (build 1.8.0_192-ea-b04)
> Java HotSpot(TM) 64-Bit Server VM (build 25.192-b04, mixed mode)
>Reporter: Kelly H Wilkerson
>Assignee: Simon Steiner
>Priority: Minor
> Fix For: main
>
> Attachments: 2920.patch, TwitterColorEmoji-SVGinOT.ttf, diff.txt,
> fail.xml, s6.patch, twe_template.fo, twe_userconfig.xml
>
>
> fop-core/src/main/java/org/apache/fop/pdf/PDFToUnicodeCMap.java
> writeBFCharEntries runs through the codepoint entries in sections of 100 at a
> time. It looks like there's an edge case here where the last entry in the
> section is a surrogate pair.
>
> Here's my steps to reproduce from the latest trunk:
> {{java -cp
> fop/target/fop-2.5.0-SNAPSHOT.jar:fop/lib/commons-logging-1.0.4.jar:fop/lib/commons-io-1.3.1.jar:fop/lib/xmlgraphics-commons-svn-trunk.jar
> org.apache.fop.fonts.apps.TTFReader TwitterColorEmoji-SVGinOT.ttf twe.xml}}
> {{java -cp
> fop/target/fop-2.5.0-SNAPSHOT.jar:fop/lib/commons-logging-1.0.4.jar:fop/lib/commons-io-1.3.1.jar:fop/lib/xmlgraphics-commons-svn-trunk.jar:fop/lib/batik-all-1.11.0-SNAPSHOT.jar
> org.apache.fop.cli.Main -c twe_userconfig.xml -xsl twe_template.fo -xml
> fail.xml -pdf fail.pdf}}
>
> Here's the temporary way I resolved it for my own build:
>
> index ee773dcec..37c21803e 100644
> --- a/fop-core/src/main/java/org/apache/fop/pdf/PDFToUnicodeCMap.java
> +++ b/fop-core/src/main/java/org/apache/fop/pdf/PDFToUnicodeCMap.java
> @@ -128,6 +128,18 @@ public class PDFToUnicodeCMap extends PDFCMap {
> while (partOfRange(charArray, charIndex)) {
> charIndex++;
> }
> /*
> * If this entry is going to overflow the entriesThisSection
> * array, then don't use it. This happens if there are
> * non-pair entries in the table mixed with pair entries.
> */
> if (Character.codePointAt(charArray, charIndex) > 0x
> && i+1 >= entriesThisSection) {
> entriesThisSection--;
> break;
> }
> writer.write("<" + padCharIndex(charIndex) + "> ");
> if (Character.codePointAt(charArray, charIndex) > 0x) {
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FOP-2920) [PATCH] Surrogate pair edge-case causes java.lang.ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/FOP-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner reassigned FOP-2920:
--
Assignee: Simon Steiner
> [PATCH] Surrogate pair edge-case causes
> java.lang.ArrayIndexOutOfBoundsException
>
>
> Key: FOP-2920
> URL: https://issues.apache.org/jira/browse/FOP-2920
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.5
> Environment: macOS Mojave
> java version "1.8.0_192-ea"
> Java(TM) SE Runtime Environment (build 1.8.0_192-ea-b04)
> Java HotSpot(TM) 64-Bit Server VM (build 25.192-b04, mixed mode)
>Reporter: Kelly H Wilkerson
>Assignee: Simon Steiner
>Priority: Minor
> Attachments: 2920.patch, TwitterColorEmoji-SVGinOT.ttf, diff.txt,
> fail.xml, s6.patch, twe_template.fo, twe_userconfig.xml
>
>
> fop-core/src/main/java/org/apache/fop/pdf/PDFToUnicodeCMap.java
> writeBFCharEntries runs through the codepoint entries in sections of 100 at a
> time. It looks like there's an edge case here where the last entry in the
> section is a surrogate pair.
>
> Here's my steps to reproduce from the latest trunk:
> {{java -cp
> fop/target/fop-2.5.0-SNAPSHOT.jar:fop/lib/commons-logging-1.0.4.jar:fop/lib/commons-io-1.3.1.jar:fop/lib/xmlgraphics-commons-svn-trunk.jar
> org.apache.fop.fonts.apps.TTFReader TwitterColorEmoji-SVGinOT.ttf twe.xml}}
> {{java -cp
> fop/target/fop-2.5.0-SNAPSHOT.jar:fop/lib/commons-logging-1.0.4.jar:fop/lib/commons-io-1.3.1.jar:fop/lib/xmlgraphics-commons-svn-trunk.jar:fop/lib/batik-all-1.11.0-SNAPSHOT.jar
> org.apache.fop.cli.Main -c twe_userconfig.xml -xsl twe_template.fo -xml
> fail.xml -pdf fail.pdf}}
>
> Here's the temporary way I resolved it for my own build:
>
> index ee773dcec..37c21803e 100644
> --- a/fop-core/src/main/java/org/apache/fop/pdf/PDFToUnicodeCMap.java
> +++ b/fop-core/src/main/java/org/apache/fop/pdf/PDFToUnicodeCMap.java
> @@ -128,6 +128,18 @@ public class PDFToUnicodeCMap extends PDFCMap {
> while (partOfRange(charArray, charIndex)) {
> charIndex++;
> }
> /*
> * If this entry is going to overflow the entriesThisSection
> * array, then don't use it. This happens if there are
> * non-pair entries in the table mixed with pair entries.
> */
> if (Character.codePointAt(charArray, charIndex) > 0x
> && i+1 >= entriesThisSection) {
> entriesThisSection--;
> break;
> }
> writer.write("<" + padCharIndex(charIndex) + "> ");
> if (Character.codePointAt(charArray, charIndex) > 0x) {
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FOP-2850) Rotated PDF files included with are misplaced
[
https://issues.apache.org/jira/browse/FOP-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner reassigned FOP-2850:
--
Assignee: Dave Roxburgh
> Rotated PDF files included with are misplaced
> ---
>
> Key: FOP-2850
> URL: https://issues.apache.org/jira/browse/FOP-2850
> Project: FOP
> Issue Type: Bug
>Affects Versions: 2.3
> Environment: Windows 10
> JDK8 64bit
> fop 2.3
> fop-pdf-images 2.3
>Reporter: Robin Jansohn
>Assignee: Dave Roxburgh
>Priority: Major
> Attachments: fop-settings.xml, test-no-rotation.pdf,
> test-rotated.pdf, test.fo, test_reproducer_4608614100576861701.pdf,
> test_workaround_1175329208771328730.pdf, workaround.fo
>
>
> I've stumbled upon an issue when including PDF files with a rotation angle
> (e.g. 90 degrees) with {{fo:external-graphic}}. The included PDF graphic
> overlaps with the previous block in the output PDF. My guess is that somehow
> width and height are mixed up in the process.
> As a workaround it is possible to undo the rotation and fix the paper size of
> the included PDF before actually creating the result PDF with FOP. In this
> case the graphic is correctly placed inside the block.
> I've attached the necessary files to this issue. I've also created a
> reproducer application on GitHub so this can be easily reproduced:
> https://github.com/jansohn/fop-rotation
>
> PDF information with rotation angle
> {noformat}
> > pdfinfo.exe -box test-rotated.pdf
> Creator:pdftk 2.02 - www.pdftk.com
> Producer: itext-paulo-155 (itextpdf.sf.net-lowagie.com)
> CreationDate: 03/06/19 15:51:18
> ModDate:03/06/19 15:51:18
> Tagged: no
> Form: none
> Pages: 1
> Encrypted: no
> Page size: 595.32 x 841.92 pts (A4) (rotated 90 degrees)
> MediaBox: 0.00 0.00 595.32 841.92
> CropBox:0.00 0.00 595.32 841.92
> BleedBox: 0.00 0.00 595.32 841.92
> TrimBox:0.00 0.00 595.32 841.92
> ArtBox: 0.00 0.00 595.32 841.92
> File size: 24801 bytes
> Optimized: no
> PDF version:1.5
> {noformat}
> PDF information without rotation angle
> {noformat}
> > pdfinfo.exe -box test-no-rotation.pdf
> Creator:pdftk 2.02 - www.pdftk.com
> Producer: itext-paulo-155 (itextpdf.sf.net-lowagie.com)
> CreationDate: 03/06/19 15:51:18
> ModDate:03/07/19 13:44:28
> Tagged: no
> Form: none
> Pages: 1
> Encrypted: no
> Page size: 842 x 596 pts (A4) (rotated 0 degrees)
> MediaBox: 0.00 -596.00 842.00 0.00
> CropBox:0.00 -596.00 842.00 0.00
> BleedBox: 0.00 -596.00 842.00 0.00
> TrimBox:0.00 -596.00 842.00 0.00
> ArtBox: 0.00 -596.00 842.00 0.00
> File size: 31578 bytes
> Optimized: no
> PDF version:1.5
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FOP-3108) [PATCH] fo:external-graphic - PDF with gradient component not displayed correctly after scaling
[
https://issues.apache.org/jira/browse/FOP-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner resolved FOP-3108.
Fix Version/s: main
Resolution: Fixed
https://github.com/apache/xmlgraphics-fop-pdf-images/commit/53e5469d1c1c6590f4ac22267686738d8710296a
> [PATCH] fo:external-graphic - PDF with gradient component not displayed
> correctly after scaling
> ---
>
> Key: FOP-3108
> URL: https://issues.apache.org/jira/browse/FOP-3108
> Project: FOP
> Issue Type: Bug
>Affects Versions: 2.7, 2.8
>Reporter: Mark Gibson
>Assignee: Simon Steiner
>Priority: Major
> Fix For: main
>
> Attachments: img-with-gradient.pdf, out1.pdf,
> patch_one_instance.diff, pdf-external-graphic-scaling-with-gradients.fo,
> sub_op.patch, submitted.patch, tiling.patch
>
>
> Using PDF-Images to inject a PDF as an image (fo:external-graphic). Image/PDF
> has a gradient fill component. When scaling the image, the gradient does not
> display properly. Resulting from shifted gradient to no gradient depending
> on scale.
> *width scaling* All issues are found when scaling width by %
> *height scaling* Doesn't seem to even scale the image
>
> Files attached for testing:
> * *{{pdf-external-graphic-scaling-with-gradients.fo}}* - the FO file, with a
> selection of image inclusions at different scales and scaling methods
> * *{{img-with-gradient.pdf}}* - the PDF image being injected in to rendered
> pdf, containing a gradient filled component.
> * *{{out1.pdf}}* - the result of running fop on above
> Tested on Windows using FOP 2.7 and 2.8
> Command used to execute is
> {{fop.bat -fo pdf-external-graphic-scaling-with-gradients.fo -pdf out1.pdf}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FOP-3108) [PATCH] fo:external-graphic - PDF with gradient component not displayed correctly after scaling
[
https://issues.apache.org/jira/browse/FOP-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner reassigned FOP-3108:
--
Assignee: Simon Steiner
> [PATCH] fo:external-graphic - PDF with gradient component not displayed
> correctly after scaling
> ---
>
> Key: FOP-3108
> URL: https://issues.apache.org/jira/browse/FOP-3108
> Project: FOP
> Issue Type: Bug
>Affects Versions: 2.7, 2.8
>Reporter: Mark Gibson
>Assignee: Simon Steiner
>Priority: Major
> Attachments: img-with-gradient.pdf, out1.pdf,
> patch_one_instance.diff, pdf-external-graphic-scaling-with-gradients.fo,
> submitted.patch
>
>
> Using PDF-Images to inject a PDF as an image (fo:external-graphic). Image/PDF
> has a gradient fill component. When scaling the image, the gradient does not
> display properly. Resulting from shifted gradient to no gradient depending
> on scale.
> *width scaling* All issues are found when scaling width by %
> *height scaling* Doesn't seem to even scale the image
>
> Files attached for testing:
> * *{{pdf-external-graphic-scaling-with-gradients.fo}}* - the FO file, with a
> selection of image inclusions at different scales and scaling methods
> * *{{img-with-gradient.pdf}}* - the PDF image being injected in to rendered
> pdf, containing a gradient filled component.
> * *{{out1.pdf}}* - the result of running fop on above
> Tested on Windows using FOP 2.7 and 2.8
> Command used to execute is
> {{fop.bat -fo pdf-external-graphic-scaling-with-gradients.fo -pdf out1.pdf}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FOP-3132) Link against Java 8 API
[ https://issues.apache.org/jira/browse/FOP-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17719299#comment-17719299 ] Simon Steiner commented on FOP-3132: https://github.com/apache/xmlgraphics-fop/commit/1fd128127811cff7c293b62992c341e75b8624b0 > Link against Java 8 API > --- > > Key: FOP-3132 > URL: https://issues.apache.org/jira/browse/FOP-3132 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > > As a user I want to compile fop with java > 8 and run with java 8 without > error > We want to be Java 8 compatible, if we compile fop with java 11, you would > currently get a error when runtime is java 8. We currently compile with java > 8, but it would be good to be able to use java 11 without a risk of issues -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FOP-3108) [PATCH] fo:external-graphic - PDF with gradient component not displayed correctly after scaling
[
https://issues.apache.org/jira/browse/FOP-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17718995#comment-17718995
]
Simon Steiner edited comment on FOP-3108 at 5/3/23 5:00 PM:
what if you use in fop.xconf
true
was (Author: ssteiner1):
what if you use
true
> [PATCH] fo:external-graphic - PDF with gradient component not displayed
> correctly after scaling
> ---
>
> Key: FOP-3108
> URL: https://issues.apache.org/jira/browse/FOP-3108
> Project: FOP
> Issue Type: Bug
>Affects Versions: 2.7, 2.8
>Reporter: Mark Gibson
>Priority: Major
> Attachments: img-with-gradient.pdf, out1.pdf,
> patch_one_instance.diff, pdf-external-graphic-scaling-with-gradients.fo
>
>
> Using PDF-Images to inject a PDF as an image (fo:external-graphic). Image/PDF
> has a gradient fill component. When scaling the image, the gradient does not
> display properly. Resulting from shifted gradient to no gradient depending
> on scale.
> *width scaling* All issues are found when scaling width by %
> *height scaling* Doesn't seem to even scale the image
>
> Files attached for testing:
> * *{{pdf-external-graphic-scaling-with-gradients.fo}}* - the FO file, with a
> selection of image inclusions at different scales and scaling methods
> * *{{img-with-gradient.pdf}}* - the PDF image being injected in to rendered
> pdf, containing a gradient filled component.
> * *{{out1.pdf}}* - the result of running fop on above
> Tested on Windows using FOP 2.7 and 2.8
> Command used to execute is
> {{fop.bat -fo pdf-external-graphic-scaling-with-gradients.fo -pdf out1.pdf}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FOP-3108) [PATCH] fo:external-graphic - PDF with gradient component not displayed correctly after scaling
[
https://issues.apache.org/jira/browse/FOP-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17718995#comment-17718995
]
Simon Steiner commented on FOP-3108:
what if you use
true
> [PATCH] fo:external-graphic - PDF with gradient component not displayed
> correctly after scaling
> ---
>
> Key: FOP-3108
> URL: https://issues.apache.org/jira/browse/FOP-3108
> Project: FOP
> Issue Type: Bug
>Affects Versions: 2.7, 2.8
>Reporter: Mark Gibson
>Priority: Major
> Attachments: img-with-gradient.pdf, out1.pdf,
> patch_one_instance.diff, pdf-external-graphic-scaling-with-gradients.fo
>
>
> Using PDF-Images to inject a PDF as an image (fo:external-graphic). Image/PDF
> has a gradient fill component. When scaling the image, the gradient does not
> display properly. Resulting from shifted gradient to no gradient depending
> on scale.
> *width scaling* All issues are found when scaling width by %
> *height scaling* Doesn't seem to even scale the image
>
> Files attached for testing:
> * *{{pdf-external-graphic-scaling-with-gradients.fo}}* - the FO file, with a
> selection of image inclusions at different scales and scaling methods
> * *{{img-with-gradient.pdf}}* - the PDF image being injected in to rendered
> pdf, containing a gradient filled component.
> * *{{out1.pdf}}* - the result of running fop on above
> Tested on Windows using FOP 2.7 and 2.8
> Command used to execute is
> {{fop.bat -fo pdf-external-graphic-scaling-with-gradients.fo -pdf out1.pdf}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (FOP-3132) Link against Java 8 API
[ https://issues.apache.org/jira/browse/FOP-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17718650#comment-17718650 ] Simon Steiner edited comment on FOP-3132 at 5/2/23 5:05 PM: -release argument is not there in java 8, so some more complexity is needed in compile steps was (Author: ssteiner1): -release argument is not there in java 8 and would mean user needs to point to java 8 rt.jar? > Link against Java 8 API > --- > > Key: FOP-3132 > URL: https://issues.apache.org/jira/browse/FOP-3132 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > > As a user I want to compile fop with java > 8 and run with java 8 without > error > We want to be Java 8 compatible, if we compile fop with java 11, you would > currently get a error when runtime is java 8. We currently compile with java > 8, but it would be good to be able to use java 11 without a risk of issues -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FOP-3132) Link against Java 8 API
[ https://issues.apache.org/jira/browse/FOP-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17718650#comment-17718650 ] Simon Steiner commented on FOP-3132: -release argument is not there in java 8 and would mean user needs to point to java 8 rt.jar? > Link against Java 8 API > --- > > Key: FOP-3132 > URL: https://issues.apache.org/jira/browse/FOP-3132 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > > As a user I want to compile fop with java > 8 and run with java 8 without > error > We want to be Java 8 compatible, if we compile fop with java 11, you would > currently get a error when runtime is java 8. We currently compile with java > 8, but it would be good to be able to use java 11 without a risk of issues -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FOP-3132) Link against Java 8 API
[ https://issues.apache.org/jira/browse/FOP-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17718614#comment-17718614 ] Simon Steiner commented on FOP-3132: If we call: new X().y(); In java 8 y() is defined in parent on X In java 11 y() is defined in X with different return type than parent method it overrides If we compile with java 11, and run with 8, it would fail > Link against Java 8 API > --- > > Key: FOP-3132 > URL: https://issues.apache.org/jira/browse/FOP-3132 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > > As a user I want to compile fop with java > 8 and run with java 8 without > error > We want to be Java 8 compatible, if we compile fop with java 11, you would > currently get a error when runtime is java 8. We currently compile with java > 8, but it would be good to be able to use java 11 without a risk of issues -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-3132) Link against Java 8 API
[ https://issues.apache.org/jira/browse/FOP-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3132. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop/commit/3d9416baf3723ee8a7d7dd4433a781a643fe9809 > Link against Java 8 API > --- > > Key: FOP-3132 > URL: https://issues.apache.org/jira/browse/FOP-3132 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > > As a user I want to compile fop with java > 8 and run with java 8 without > error > We want to be Java 8 compatible, if we compile fop with java 11, you would > currently get a error when runtime is java 8. We currently compile with java > 8, but it would be good to be able to use java 11 without a risk of issues -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3132) Link against Java 8 API
[ https://issues.apache.org/jira/browse/FOP-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3132: --- Description: As a user I want to compile fop with java > 8 and run with java 8 without error We want to be Java 8 compatible, if we compile fop with java 11, you would currently get a error when runtime is java 8. We currently compile with java 8, but it would be good to be able to use java 11 without a risk of issues was:x > Link against Java 8 API > --- > > Key: FOP-3132 > URL: https://issues.apache.org/jira/browse/FOP-3132 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > > As a user I want to compile fop with java > 8 and run with java 8 without > error > We want to be Java 8 compatible, if we compile fop with java 11, you would > currently get a error when runtime is java 8. We currently compile with java > 8, but it would be good to be able to use java 11 without a risk of issues -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3132) Link against Java 8 API
Simon Steiner created FOP-3132: -- Summary: Link against Java 8 API Key: FOP-3132 URL: https://issues.apache.org/jira/browse/FOP-3132 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FOP-3131) AFP with custom font TTF generates space-letter-space
[ https://issues.apache.org/jira/browse/FOP-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17718483#comment-17718483 ] Simon Steiner commented on FOP-3131: "In the example below you see that the words are not generated words by words but space-letter-space which is causing problems when printing." wont position-by-char="false" affect this statement > AFP with custom font TTF generates space-letter-space > - > > Key: FOP-3131 > URL: https://issues.apache.org/jira/browse/FOP-3131 > Project: FOP > Issue Type: Bug > Components: font/unqualified >Affects Versions: 2.8 > Environment: FOP 2.8 > Java 17 > Ubuntu 22.04 >Reporter: jo Heinen >Priority: Major > Attachments: afpFontCustom.afp, arial.ttf, fo.xsl, fop.xconf, > spacemono-regular.ttf, times.ttf > > > I am producing an AFP file with Apache FOP 2.8 and java 17. > In my fo.xconf file am using a custom font with the TTF format and I have > used also a xsl file. > I have tried several TTF and tried also the attribute > _position-by-char="false"._ > Altough the file renders properly when viewed with a tool like "Papyrus AFP > viewer", > I have noticed that the content has issues when analyzed using AFPexplorer. > In the example below you see that the words are not generated words by words > but space-letter-space which is causing problems when printing. > *FPexplorer* > MDR: 1= A r i a l 2= a r i a l N 3= a r i a l N > > PTX tag: > A r i a l a r i a l N a r i a l N B > ESC > AMB 223 > AMI 236 > SCFL 1SVI 11 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-3130) Correct font differences table for Chrome
[ https://issues.apache.org/jira/browse/FOP-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3130. Fix Version/s: main Resolution: Fixed https://gitbox.apache.org/repos/asf?p=xmlgraphics-fop.git;a=commit;h=387218dde1dcc8b7bf68065ae5b78411c45a89d6 > Correct font differences table for Chrome > - > > Key: FOP-3130 > URL: https://issues.apache.org/jira/browse/FOP-3130 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > Attachments: fop.xconf > > > Correct differences table when using merge-fonts feature -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3130) Correct font differences table for Chrome
Simon Steiner created FOP-3130: -- Summary: Correct font differences table for Chrome Key: FOP-3130 URL: https://issues.apache.org/jira/browse/FOP-3130 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner Attachments: fop.xconf -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3130) Correct font differences table for Chrome
[ https://issues.apache.org/jira/browse/FOP-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3130: --- Description: Correct differences table when using merge-fonts feature > Correct font differences table for Chrome > - > > Key: FOP-3130 > URL: https://issues.apache.org/jira/browse/FOP-3130 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf > > > Correct differences table when using merge-fonts feature -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3130) Correct font differences table for Chrome
[ https://issues.apache.org/jira/browse/FOP-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3130: --- Attachment: fop.xconf > Correct font differences table for Chrome > - > > Key: FOP-3130 > URL: https://issues.apache.org/jira/browse/FOP-3130 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-3129) Symbol font was not being mapped to unicode
[ https://issues.apache.org/jira/browse/FOP-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3129. Fix Version/s: main Resolution: Fixed https://gitbox.apache.org/repos/asf?p=xmlgraphics-fop.git;a=commit;h=6696559fc657aa3d83b868c337ced59e6a44ca7b > Symbol font was not being mapped to unicode > --- > > Key: FOP-3129 > URL: https://issues.apache.org/jira/browse/FOP-3129 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > Attachments: fop.xconf, test.fo > > > fop test.fo -c fop.xconf out.pdf > Glyphs should show in output > WARNING: Glyph "D" (0x44, D) not available in font "TROYE-13BLAND". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3129) Symbol font was not being mapped to unicode
[ https://issues.apache.org/jira/browse/FOP-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3129: --- Description: fop test.fo -c fop.xconf out.pdf Glyphs should show in output WARNING: Glyph "D" (0x44, D) not available in font "TROYE-13BLAND". > Symbol font was not being mapped to unicode > --- > > Key: FOP-3129 > URL: https://issues.apache.org/jira/browse/FOP-3129 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, test.fo > > > fop test.fo -c fop.xconf out.pdf > Glyphs should show in output > WARNING: Glyph "D" (0x44, D) not available in font "TROYE-13BLAND". -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3129) Symbol font was not being mapped to unicode
[ https://issues.apache.org/jira/browse/FOP-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3129: --- Attachment: fop.xconf test.fo > Symbol font was not being mapped to unicode > --- > > Key: FOP-3129 > URL: https://issues.apache.org/jira/browse/FOP-3129 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, test.fo > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3129) Symbol font was not being mapped to unicode
Simon Steiner created FOP-3129: -- Summary: Symbol font was not being mapped to unicode Key: FOP-3129 URL: https://issues.apache.org/jira/browse/FOP-3129 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FOP-3090) [PATCH] Incorrect page creation with master-reference="singlePage" page-position="only"/>
[
https://issues.apache.org/jira/browse/FOP-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17709349#comment-17709349
]
Simon Steiner edited comment on FOP-3090 at 4/6/23 11:59 AM:
-
https://gitbox.apache.org/repos/asf?p=xmlgraphics-fop.git;a=commit;h=95ddfc80503820b6cd5d07121595f6419cfbe221
https://gitbox.apache.org/repos/asf?p=xmlgraphics-website.git;a=commit;h=12cd9b4fc4ee105434dfa82574dc38f4220d5d85
was (Author: ssteiner1):
https://gitbox.apache.org/repos/asf?p=xmlgraphics-fop.git;a=commit;h=95ddfc80503820b6cd5d07121595f6419cfbe221
> [PATCH] Incorrect page creation with master-reference="singlePage"
> page-position="only"/>
> -
>
> Key: FOP-3090
> URL: https://issues.apache.org/jira/browse/FOP-3090
> Project: FOP
> Issue Type: Bug
> Components: layout/page
>Affects Versions: 2.7
> Environment: Windows 10
>Reporter: Franziska Zäch
>Assignee: Simon Steiner
>Priority: Major
> Fix For: main
>
> Attachments: Codelist_Template.xsl, CommonTemplateFO.xsl,
> INVOICFO.xsl, INVOICFO.xsl, Mustermann.2.7.pdf, Mustermann.pdf,
> Mustermann.xml, Mustermann.xml, Mustermann_Test_2.7.pdf,
> Mustermann_big_ok.xml, Mustermann_big_ok.xml, Mustermann_big_ok.xml.pdf,
> Mustermann_big_ok.xml.pdf, Mustermann_short_ok.xml,
> Mustermann_short_ok.xml.pdf, TextAusgabePDF.xml, fop_invoic.bat,
> patch_xmlgraphics-fop_FOP-3090_02.diff,
> patch_xmlgraphics-website_FOP-3090_02.diff
>
>
> After upgrading FOP 1. 1 to FOP 2. 7, the “Single Page” is no longer created
> correctly if a 2nd page is to be created due to the data volume in “body” and
> a region-after extent=”11. 8cm.
> See appendix template. pdf: Here a 2nd page is created due to the data volume
> (body)!
> See Appendix Mustermann 2. 7. pdf: Due to the data volume (body) a 2nd page
> should be created here!
> Note: the bank details should only be printed once per document!
> Note: with the FOP version 2. 6 the PDF is created correctly!
> page-height="297mm" page-width="210mm" margin-top="15mm" margin-bottom="0mm"
> margin-left="3mm" margin-right="2mm">
> margin-top="2.4cm" margin-b{color:#ff}ottom="11.8cm{color}"
> margin-left="10mm"/>
> region-name="xsl-region-before"/>
> <{color:#ff}fo:region-after extent="11.8cm{color}"
> region-name="last-region-after" margin-right="40mm" display-align="after"/>
> region-name="xsl-region-start"/>
>
>
>
>
> master-reference="singlePage" page-position="only"/>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FOP-3090) [PATCH] Incorrect page creation with master-reference="singlePage" page-position="only"/>
[
https://issues.apache.org/jira/browse/FOP-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17709351#comment-17709351
]
Simon Steiner commented on FOP-3090:
To use this, add to fop.xconf after :
false
> [PATCH] Incorrect page creation with master-reference="singlePage"
> page-position="only"/>
> -
>
> Key: FOP-3090
> URL: https://issues.apache.org/jira/browse/FOP-3090
> Project: FOP
> Issue Type: Bug
> Components: layout/page
>Affects Versions: 2.7
> Environment: Windows 10
>Reporter: Franziska Zäch
>Assignee: Simon Steiner
>Priority: Major
> Fix For: main
>
> Attachments: Codelist_Template.xsl, CommonTemplateFO.xsl,
> INVOICFO.xsl, INVOICFO.xsl, Mustermann.2.7.pdf, Mustermann.pdf,
> Mustermann.xml, Mustermann.xml, Mustermann_Test_2.7.pdf,
> Mustermann_big_ok.xml, Mustermann_big_ok.xml, Mustermann_big_ok.xml.pdf,
> Mustermann_big_ok.xml.pdf, Mustermann_short_ok.xml,
> Mustermann_short_ok.xml.pdf, TextAusgabePDF.xml, fop_invoic.bat,
> patch_xmlgraphics-fop_FOP-3090_02.diff,
> patch_xmlgraphics-website_FOP-3090_02.diff
>
>
> After upgrading FOP 1. 1 to FOP 2. 7, the “Single Page” is no longer created
> correctly if a 2nd page is to be created due to the data volume in “body” and
> a region-after extent=”11. 8cm.
> See appendix template. pdf: Here a 2nd page is created due to the data volume
> (body)!
> See Appendix Mustermann 2. 7. pdf: Due to the data volume (body) a 2nd page
> should be created here!
> Note: the bank details should only be printed once per document!
> Note: with the FOP version 2. 6 the PDF is created correctly!
> page-height="297mm" page-width="210mm" margin-top="15mm" margin-bottom="0mm"
> margin-left="3mm" margin-right="2mm">
> margin-top="2.4cm" margin-b{color:#ff}ottom="11.8cm{color}"
> margin-left="10mm"/>
> region-name="xsl-region-before"/>
> <{color:#ff}fo:region-after extent="11.8cm{color}"
> region-name="last-region-after" margin-right="40mm" display-align="after"/>
> region-name="xsl-region-start"/>
>
>
>
>
> master-reference="singlePage" page-position="only"/>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FOP-3090) [PATCH] Incorrect page creation with master-reference="singlePage" page-position="only"/>
[
https://issues.apache.org/jira/browse/FOP-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner resolved FOP-3090.
Fix Version/s: main
Resolution: Fixed
https://gitbox.apache.org/repos/asf?p=xmlgraphics-fop.git;a=commit;h=95ddfc80503820b6cd5d07121595f6419cfbe221
> [PATCH] Incorrect page creation with master-reference="singlePage"
> page-position="only"/>
> -
>
> Key: FOP-3090
> URL: https://issues.apache.org/jira/browse/FOP-3090
> Project: FOP
> Issue Type: Bug
> Components: layout/page
>Affects Versions: 2.7
> Environment: Windows 10
>Reporter: Franziska Zäch
>Assignee: Simon Steiner
>Priority: Major
> Fix For: main
>
> Attachments: Codelist_Template.xsl, CommonTemplateFO.xsl,
> INVOICFO.xsl, INVOICFO.xsl, Mustermann.2.7.pdf, Mustermann.pdf,
> Mustermann.xml, Mustermann.xml, Mustermann_Test_2.7.pdf,
> Mustermann_big_ok.xml, Mustermann_big_ok.xml, Mustermann_big_ok.xml.pdf,
> Mustermann_big_ok.xml.pdf, Mustermann_short_ok.xml,
> Mustermann_short_ok.xml.pdf, TextAusgabePDF.xml, fop_invoic.bat,
> patch_xmlgraphics-fop_FOP-3090_02.diff,
> patch_xmlgraphics-website_FOP-3090_02.diff
>
>
> After upgrading FOP 1. 1 to FOP 2. 7, the “Single Page” is no longer created
> correctly if a 2nd page is to be created due to the data volume in “body” and
> a region-after extent=”11. 8cm.
> See appendix template. pdf: Here a 2nd page is created due to the data volume
> (body)!
> See Appendix Mustermann 2. 7. pdf: Due to the data volume (body) a 2nd page
> should be created here!
> Note: the bank details should only be printed once per document!
> Note: with the FOP version 2. 6 the PDF is created correctly!
> page-height="297mm" page-width="210mm" margin-top="15mm" margin-bottom="0mm"
> margin-left="3mm" margin-right="2mm">
> margin-top="2.4cm" margin-b{color:#ff}ottom="11.8cm{color}"
> margin-left="10mm"/>
> region-name="xsl-region-before"/>
> <{color:#ff}fo:region-after extent="11.8cm{color}"
> region-name="last-region-after" margin-right="40mm" display-align="after"/>
> region-name="xsl-region-start"/>
>
>
>
>
> master-reference="singlePage" page-position="only"/>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FOP-3090) [PATCH] Incorrect page creation with master-reference="singlePage" page-position="only"/>
[
https://issues.apache.org/jira/browse/FOP-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner reassigned FOP-3090:
--
Assignee: Simon Steiner
> [PATCH] Incorrect page creation with master-reference="singlePage"
> page-position="only"/>
> -
>
> Key: FOP-3090
> URL: https://issues.apache.org/jira/browse/FOP-3090
> Project: FOP
> Issue Type: Bug
> Components: layout/page
>Affects Versions: 2.7
> Environment: Windows 10
>Reporter: Franziska Zäch
>Assignee: Simon Steiner
>Priority: Major
> Attachments: Codelist_Template.xsl, CommonTemplateFO.xsl,
> INVOICFO.xsl, INVOICFO.xsl, Mustermann.2.7.pdf, Mustermann.pdf,
> Mustermann.xml, Mustermann.xml, Mustermann_Test_2.7.pdf,
> Mustermann_big_ok.xml, Mustermann_big_ok.xml, Mustermann_big_ok.xml.pdf,
> Mustermann_big_ok.xml.pdf, Mustermann_short_ok.xml,
> Mustermann_short_ok.xml.pdf, TextAusgabePDF.xml, fop_invoic.bat,
> patch_xmlgraphics-fop_FOP-3090_02.diff,
> patch_xmlgraphics-website_FOP-3090_02.diff
>
>
> After upgrading FOP 1. 1 to FOP 2. 7, the “Single Page” is no longer created
> correctly if a 2nd page is to be created due to the data volume in “body” and
> a region-after extent=”11. 8cm.
> See appendix template. pdf: Here a 2nd page is created due to the data volume
> (body)!
> See Appendix Mustermann 2. 7. pdf: Due to the data volume (body) a 2nd page
> should be created here!
> Note: the bank details should only be printed once per document!
> Note: with the FOP version 2. 6 the PDF is created correctly!
> page-height="297mm" page-width="210mm" margin-top="15mm" margin-bottom="0mm"
> margin-left="3mm" margin-right="2mm">
> margin-top="2.4cm" margin-b{color:#ff}ottom="11.8cm{color}"
> margin-left="10mm"/>
> region-name="xsl-region-before"/>
> <{color:#ff}fo:region-after extent="11.8cm{color}"
> region-name="last-region-after" margin-right="40mm" display-align="after"/>
> region-name="xsl-region-start"/>
>
>
>
>
> master-reference="singlePage" page-position="only"/>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FOP-3127) Allow XMP at PDF page level
[ https://issues.apache.org/jira/browse/FOP-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3127. Fix Version/s: main Resolution: Fixed https://gitbox.apache.org/repos/asf?p=xmlgraphics-commons.git;a=commit;h=17d29e4481bcf63275a8ed70ff2ec28c373f2789 https://gitbox.apache.org/repos/asf?p=xmlgraphics-fop.git;a=commit;h=b7eeb45bea9fa9fbc462a338c84d65876da263c7 > Allow XMP at PDF page level > --- > > Key: FOP-3127 > URL: https://issues.apache.org/jira/browse/FOP-3127 > Project: FOP > Issue Type: Improvement >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > Attachments: simple.fo > > > fop simple.fo out.pdf > Open pdf in a text editor you should see abc:def="val" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3127) Allow XMP at PDF page level
[ https://issues.apache.org/jira/browse/FOP-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3127: --- Attachment: simple.fo > Allow XMP at PDF page level > --- > > Key: FOP-3127 > URL: https://issues.apache.org/jira/browse/FOP-3127 > Project: FOP > Issue Type: Improvement >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: simple.fo > > > fop test.fo out.pdf > Open pdf in a text editor you should see abc:def="val" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3127) Allow XMP at PDF page level
[ https://issues.apache.org/jira/browse/FOP-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3127: --- Description: fop simple.fo out.pdf Open pdf in a text editor you should see abc:def="val" was: fop test.fo out.pdf Open pdf in a text editor you should see abc:def="val" > Allow XMP at PDF page level > --- > > Key: FOP-3127 > URL: https://issues.apache.org/jira/browse/FOP-3127 > Project: FOP > Issue Type: Improvement >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: simple.fo > > > fop simple.fo out.pdf > Open pdf in a text editor you should see abc:def="val" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3127) Allow XMP at PDF page level
[ https://issues.apache.org/jira/browse/FOP-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3127: --- Description: fop test.fo out.pdf Open pdf in a text editor you should see abc:def="val" > Allow XMP at PDF page level > --- > > Key: FOP-3127 > URL: https://issues.apache.org/jira/browse/FOP-3127 > Project: FOP > Issue Type: Improvement >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > > fop test.fo out.pdf > Open pdf in a text editor you should see abc:def="val" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3127) Allow XMP at PDF page level
Simon Steiner created FOP-3127: -- Summary: Allow XMP at PDF page level Key: FOP-3127 URL: https://issues.apache.org/jira/browse/FOP-3127 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3126) Add Extensions For PostScript to html docs
Simon Steiner created FOP-3126: -- Summary: Add Extensions For PostScript to html docs Key: FOP-3126 URL: https://issues.apache.org/jira/browse/FOP-3126 Project: FOP Issue Type: Bug Reporter: Simon Steiner https://cwiki.apache.org/confluence/display/XMLGRAPHICSFOP/ExtensionsForPostScript -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3126) Add Extensions For PostScript to html docs
[ https://issues.apache.org/jira/browse/FOP-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3126: --- Description: https://cwiki.apache.org/confluence/display/XMLGRAPHICSFOP/ExtensionsForPostScript should be on https://xmlgraphics.apache.org/fop/ site was:https://cwiki.apache.org/confluence/display/XMLGRAPHICSFOP/ExtensionsForPostScript > Add Extensions For PostScript to html docs > -- > > Key: FOP-3126 > URL: https://issues.apache.org/jira/browse/FOP-3126 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Priority: Major > > https://cwiki.apache.org/confluence/display/XMLGRAPHICSFOP/ExtensionsForPostScript > should be on https://xmlgraphics.apache.org/fop/ site -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-3125) NPE when using broken link and PDF 1.5
[ https://issues.apache.org/jira/browse/FOP-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3125. Fix Version/s: main Resolution: Fixed https://gitbox.apache.org/repos/asf?p=xmlgraphics-fop.git;a=commit;h=45f68e349e3f870fee5d4604fcc8115938484c52 > NPE when using broken link and PDF 1.5 > -- > > Key: FOP-3125 > URL: https://issues.apache.org/jira/browse/FOP-3125 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > Attachments: fop.xconf, simple.fo > > > fop simple.fo -c fop.xconf -if application/pdf out.if > fop -c fop.xconf -ifin out.if out.pdf > java.lang.NullPointerException > at > org.apache.fop.pdf.xref.CrossReferenceStream.output(CrossReferenceStream.java:91) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3125) NPE when using broken link and PDF 1.5
[ https://issues.apache.org/jira/browse/FOP-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3125: --- Description: fop simple.fo -c fop.xconf -if application/pdf out.if fop -c fop.xconf -ifin out.if out.pdf java.lang.NullPointerException at org.apache.fop.pdf.xref.CrossReferenceStream.output(CrossReferenceStream.java:91) > NPE when using broken link and PDF 1.5 > -- > > Key: FOP-3125 > URL: https://issues.apache.org/jira/browse/FOP-3125 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, simple.fo > > > fop simple.fo -c fop.xconf -if application/pdf out.if > fop -c fop.xconf -ifin out.if out.pdf > java.lang.NullPointerException > at > org.apache.fop.pdf.xref.CrossReferenceStream.output(CrossReferenceStream.java:91) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3125) NPE when using broken link and PDF 1.5
Simon Steiner created FOP-3125: -- Summary: NPE when using broken link and PDF 1.5 Key: FOP-3125 URL: https://issues.apache.org/jira/browse/FOP-3125 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner Attachments: fop.xconf, simple.fo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3125) NPE when using broken link and PDF 1.5
[ https://issues.apache.org/jira/browse/FOP-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3125: --- Attachment: fop.xconf simple.fo > NPE when using broken link and PDF 1.5 > -- > > Key: FOP-3125 > URL: https://issues.apache.org/jira/browse/FOP-3125 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, simple.fo > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-1722) [PATCH] Values in PDF Number Trees must be indirect references
[ https://issues.apache.org/jira/browse/FOP-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-1722. Fix Version/s: main Assignee: Simon Steiner Resolution: Fixed https://gitbox.apache.org/repos/asf?p=xmlgraphics-fop.git;a=commit;h=120b50fdf64cf9c2a52c86d9ca4e9340dbd2715f > [PATCH] Values in PDF Number Trees must be indirect references > -- > > Key: FOP-1722 > URL: https://issues.apache.org/jira/browse/FOP-1722 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.5 > Environment: Operating System: All > Platform: All >Reporter: Vincent Hennebert >Assignee: Simon Steiner > Fix For: main > > Attachments: patch3.txt, text.fo, text.pdf > > > See PDF Reference, Third Edition, Section 3.8.5, "Number Trees": the Nums > entry > must be an array of key-value pairs where value is an indirect reference to > the > object associated with the key. > However, the o.a.f.pdf.PDFNumsArray class does nothing to ensure that elements > added to the array are actually indirectly referenced. So generated PDFs are > strictly speaking invalid. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-3113) [PATCH] Build documentation omission (maven)
[ https://issues.apache.org/jira/browse/FOP-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3113. Fix Version/s: 2.8 Resolution: Fixed https://gitbox.apache.org/repos/asf?p=xmlgraphics-website.git;a=commit;h=7671110548ec67fd87e774c6d1af2fd07c17a0b8 > [PATCH] Build documentation omission (maven) > > > Key: FOP-3113 > URL: https://issues.apache.org/jira/browse/FOP-3113 > Project: FOP > Issue Type: Bug > Components: documentation >Affects Versions: 2.8 >Reporter: Dave Roxburgh >Assignee: Simon Steiner >Priority: Trivial > Labels: newbie > Fix For: 2.8 > > Attachments: FOP-3113-patch.txt, FOP-3113-patch2.diff > > > Following build instructions at: > [https://xmlgraphics.apache.org/fop/2.8/compiling.html] > ... the ant build failed due to dependency on maven. After installing maven, > the build succeeded. > The build instructions need updating to indicate the maven dependency. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FOP-3113) [PATCH] Build documentation omission (maven)
[ https://issues.apache.org/jira/browse/FOP-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner reassigned FOP-3113: -- Assignee: Simon Steiner > [PATCH] Build documentation omission (maven) > > > Key: FOP-3113 > URL: https://issues.apache.org/jira/browse/FOP-3113 > Project: FOP > Issue Type: Bug > Components: documentation >Affects Versions: 2.8 >Reporter: Dave Roxburgh >Assignee: Simon Steiner >Priority: Trivial > Labels: newbie > Attachments: FOP-3113-patch.txt, FOP-3113-patch2.diff > > > Following build instructions at: > [https://xmlgraphics.apache.org/fop/2.8/compiling.html] > ... the ant build failed due to dependency on maven. After installing maven, > the build succeeded. > The build instructions need updating to indicate the maven dependency. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-3090) Incorrect page creation with master-reference="singlePage" page-position="only"/>
[
https://issues.apache.org/jira/browse/FOP-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner resolved FOP-3090.
Resolution: Not A Problem
> Incorrect page creation with master-reference="singlePage"
> page-position="only"/>
> -
>
> Key: FOP-3090
> URL: https://issues.apache.org/jira/browse/FOP-3090
> Project: FOP
> Issue Type: Bug
> Components: layout/page
>Affects Versions: 2.7
> Environment: Windows 10
>Reporter: Franziska Zäch
>Priority: Major
> Attachments: Codelist_Template.xsl, CommonTemplateFO.xsl,
> INVOICFO.xsl, Mustermann.2.7.pdf, Mustermann.pdf, TextAusgabePDF.xml,
> fop_invoic.bat
>
>
> After upgrading FOP 1. 1 to FOP 2. 7, the “Single Page” is no longer created
> correctly if a 2nd page is to be created due to the data volume in “body” and
> a region-after extent=”11. 8cm.
> See appendix template. pdf: Here a 2nd page is created due to the data volume
> (body)!
> See Appendix Mustermann 2. 7. pdf: Due to the data volume (body) a 2nd page
> should be created here!
> Note: the bank details should only be printed once per document!
> Note: with the FOP version 2. 6 the PDF is created correctly!
> page-height="297mm" page-width="210mm" margin-top="15mm" margin-bottom="0mm"
> margin-left="3mm" margin-right="2mm">
> margin-top="2.4cm" margin-b{color:#ff}ottom="11.8cm{color}"
> margin-left="10mm"/>
> region-name="xsl-region-before"/>
> <{color:#ff}fo:region-after extent="11.8cm{color}"
> region-name="last-region-after" margin-right="40mm" display-align="after"/>
> region-name="xsl-region-start"/>
>
>
>
>
> master-reference="singlePage" page-position="only"/>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FOP-3124) Subrs data missing from font merging
[ https://issues.apache.org/jira/browse/FOP-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3124. Fix Version/s: main Resolution: Fixed https://gitbox.apache.org/repos/asf?p=xmlgraphics-fop-pdf-images.git;a=commit;h=f11ef0941991887dec015407ab58e36bc2b64232 > Subrs data missing from font merging > > > Key: FOP-3124 > URL: https://issues.apache.org/jira/browse/FOP-3124 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > Attachments: cffsubrs.pdf, cffsubrs2.pdf, fop.xconf, test.fo > > > fop test.fo -c fop.xconf out.pdf > There should be no error when viewing the PDF -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3124) Subrs data missing from font merging
[ https://issues.apache.org/jira/browse/FOP-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3124: --- Description: fop test.fo -c fop.xconf out.pdf There should be no error when viewing the PDF > Subrs data missing from font merging > > > Key: FOP-3124 > URL: https://issues.apache.org/jira/browse/FOP-3124 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: cffsubrs.pdf, cffsubrs2.pdf, fop.xconf, test.fo > > > fop test.fo -c fop.xconf out.pdf > There should be no error when viewing the PDF -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3124) Subrs data missing from font merging
Simon Steiner created FOP-3124: -- Summary: Subrs data missing from font merging Key: FOP-3124 URL: https://issues.apache.org/jira/browse/FOP-3124 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner Attachments: cffsubrs.pdf, cffsubrs2.pdf, fop.xconf, test.fo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3124) Subrs data missing from font merging
[ https://issues.apache.org/jira/browse/FOP-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3124: --- Attachment: cffsubrs.pdf cffsubrs2.pdf fop.xconf test.fo > Subrs data missing from font merging > > > Key: FOP-3124 > URL: https://issues.apache.org/jira/browse/FOP-3124 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: cffsubrs.pdf, cffsubrs2.pdf, fop.xconf, test.fo > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-1722) [PATCH] Values in PDF Number Trees must be indirect references
[ https://issues.apache.org/jira/browse/FOP-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-1722: --- Summary: [PATCH] Values in PDF Number Trees must be indirect references (was: Values in PDF Number Trees must be indirect references) > [PATCH] Values in PDF Number Trees must be indirect references > -- > > Key: FOP-1722 > URL: https://issues.apache.org/jira/browse/FOP-1722 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.5 > Environment: Operating System: All > Platform: All >Reporter: Vincent Hennebert > Attachments: patch3.txt, text.fo, text.pdf > > > See PDF Reference, Third Edition, Section 3.8.5, "Number Trees": the Nums > entry > must be an array of key-value pairs where value is an indirect reference to > the > object associated with the key. > However, the o.a.f.pdf.PDFNumsArray class does nothing to ensure that elements > added to the array are actually indirectly referenced. So generated PDFs are > strictly speaking invalid. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-3123) Modified stream should be used in the cache key
[ https://issues.apache.org/jira/browse/FOP-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3123. Fix Version/s: main Resolution: Fixed https://gitbox.apache.org/repos/asf?p=xmlgraphics-fop-pdf-images.git;a=commit;h=13dc9e576730de702c27a7d9fb61d11fbcb0c818 > Modified stream should be used in the cache key > --- > > Key: FOP-3123 > URL: https://issues.apache.org/jira/browse/FOP-3123 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > > When pdf-plugin creates a hashcode for a stream it should use the hash of the > updated stream -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3123) Modified stream should be used in the cache key
[ https://issues.apache.org/jira/browse/FOP-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3123: --- Description: When pdf-plugin creates a hashcode for a stream it should use the hash of the updated stream > Modified stream should be used in the cache key > --- > > Key: FOP-3123 > URL: https://issues.apache.org/jira/browse/FOP-3123 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > > When pdf-plugin creates a hashcode for a stream it should use the hash of the > updated stream -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3123) Modified stream should be used in the cache key
Simon Steiner created FOP-3123: -- Summary: Modified stream should be used in the cache key Key: FOP-3123 URL: https://issues.apache.org/jira/browse/FOP-3123 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FOP-3098) [PATCH] Nullpointer Exception in LMiter.next depending on text
[
https://issues.apache.org/jira/browse/FOP-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698432#comment-17698432
]
Simon Steiner commented on FOP-3098:
The svn repo is no longer used
> [PATCH] Nullpointer Exception in LMiter.next depending on text
> --
>
> Key: FOP-3098
> URL: https://issues.apache.org/jira/browse/FOP-3098
> Project: FOP
> Issue Type: Bug
> Components: fo/unqualified
>Affects Versions: 2.7
> Environment: Windows 10
>Reporter: Michael Heitkamp
>Assignee: Chris Bowditch
>Priority: Major
> Attachments: Post-FOP-3098-NPE-Bugfix.diff, patch.txt,
> patch_cached.txt, stacktrace.txt, x-fop-error.xml, x-fop-error.xsl
>
>
> Doing a FOP translation with the given XSL and XML input files lead to a
> Nullpointer Exception.
> If the text block is shortened by one character ("dataX" -> "data") then the
> translation succeeds.
> If the text block is replaced by "lore ipsum" of the same length then the
> translation succeeds also.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FOP-3121) Table width may be too wide when layout width changes
[ https://issues.apache.org/jira/browse/FOP-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3121. Fix Version/s: trunk Resolution: Fixed https://gitbox.apache.org/repos/asf?p=xmlgraphics-fop.git;a=commit;h=f4205e68b07a965481f326515ba33f08490ebc0a > Table width may be too wide when layout width changes > - > > Key: FOP-3121 > URL: https://issues.apache.org/jira/browse/FOP-3121 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > Attachments: test.fo > > > fop test.fo out.pdf > Table border on 2nd page should have a even width -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3121) Table width may be too wide when layout width changes
[ https://issues.apache.org/jira/browse/FOP-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3121: --- Description: fop test.fo out.pdf Table border on 2nd page should have a even width > Table width may be too wide when layout width changes > - > > Key: FOP-3121 > URL: https://issues.apache.org/jira/browse/FOP-3121 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test.fo > > > fop test.fo out.pdf > Table border on 2nd page should have a even width -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3121) Table width may be too wide when layout width changes
[ https://issues.apache.org/jira/browse/FOP-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3121: --- Attachment: test.fo > Table width may be too wide when layout width changes > - > > Key: FOP-3121 > URL: https://issues.apache.org/jira/browse/FOP-3121 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test.fo > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
