[jira] [Resolved] (FOP-3178) [PATCH] On-Demand Table Layout issue when there are pages of different widths
[ https://issues.apache.org/jira/browse/FOP-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3178. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop/commit/c7660fe84c7eabdb41c3aa88970f45401df72991 > [PATCH] On-Demand Table Layout issue when there are pages of different widths > - > > Key: FOP-3178 > URL: https://issues.apache.org/jira/browse/FOP-3178 > Project: FOP > Issue Type: Bug >Reporter: João André Gonçalves >Assignee: Simon Steiner >Priority: Minor > Fix For: main > > Attachments: fop.patch > > > The tables don’t always seem to be rendered correctly when there's an IPD > change between pages -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FOP-3178) [PATCH] On-Demand Table Layout issue when there are pages of different widths
[ https://issues.apache.org/jira/browse/FOP-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner reassigned FOP-3178: -- Assignee: Simon Steiner > [PATCH] On-Demand Table Layout issue when there are pages of different widths > - > > Key: FOP-3178 > URL: https://issues.apache.org/jira/browse/FOP-3178 > Project: FOP > Issue Type: Bug >Reporter: João André Gonçalves >Assignee: Simon Steiner >Priority: Minor > Attachments: fop.patch > > > The tables don’t always seem to be rendered correctly when there's an IPD > change between pages -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-3177) FO wrapper should not add space to a document
[ https://issues.apache.org/jira/browse/FOP-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3177. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop/commit/7b29d1d1354f07a5e2914c0f2711d50f7c2ff967 > FO wrapper should not add space to a document > - > > Key: FOP-3177 > URL: https://issues.apache.org/jira/browse/FOP-3177 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > Attachments: simple.fo > > > fop simple.fo out.pdf > black box should be touching the top of yellow area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3177) FO wrapper should not add space to a document
[ https://issues.apache.org/jira/browse/FOP-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3177: --- Attachment: simple.fo > FO wrapper should not add space to a document > - > > Key: FOP-3177 > URL: https://issues.apache.org/jira/browse/FOP-3177 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: simple.fo > > > black box should be touching the top of yellow area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3177) FO wrapper should not add space to a document
[ https://issues.apache.org/jira/browse/FOP-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3177: --- Description: fop simple.fo out.pdf black box should be touching the top of yellow area was:black box should be touching the top of yellow area > FO wrapper should not add space to a document > - > > Key: FOP-3177 > URL: https://issues.apache.org/jira/browse/FOP-3177 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: simple.fo > > > fop simple.fo out.pdf > black box should be touching the top of yellow area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3177) FO wrapper should not add space to a document
[ https://issues.apache.org/jira/browse/FOP-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3177: --- Description: black box should be touching the top of yellow area > FO wrapper should not add space to a document > - > > Key: FOP-3177 > URL: https://issues.apache.org/jira/browse/FOP-3177 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: simple.fo > > > black box should be touching the top of yellow area -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3177) FO wrapper should not add space to a document
Simon Steiner created FOP-3177: -- Summary: FO wrapper should not add space to a document Key: FOP-3177 URL: https://issues.apache.org/jira/browse/FOP-3177 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3176) Remove unused PDFStructElem
[ https://issues.apache.org/jira/browse/FOP-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3176: --- Description: fop simple.fo -c fop.xconf out.pdf Open PDF in acrobat, no error is displayed after running accessibility check was: fop test.fo -c fop.xconf out.pdf Open PDF in acrobat, no error is displayed after running accessibility check > Remove unused PDFStructElem > --- > > Key: FOP-3176 > URL: https://issues.apache.org/jira/browse/FOP-3176 > 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 out.pdf > Open PDF in acrobat, no error is displayed after running accessibility check -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3176) Remove unused PDFStructElem
[ https://issues.apache.org/jira/browse/FOP-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3176: --- Description: fop test.fo -c fop.xconf out.pdf Open PDF in acrobat, no error is displayed after running accessibility check was: test.fo -c fop.xconf out.pdf Open PDF in acrobat, no error is displayed after running accessibility check > Remove unused PDFStructElem > --- > > Key: FOP-3176 > URL: https://issues.apache.org/jira/browse/FOP-3176 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > Attachments: fop.xconf, simple.fo > > > fop test.fo -c fop.xconf out.pdf > Open PDF in acrobat, no error is displayed after running accessibility check -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-3176) Remove unused PDFStructElem
[ https://issues.apache.org/jira/browse/FOP-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3176. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop/commit/1484cf87fea058f6908d57491dfde439cb9bec4b > Remove unused PDFStructElem > --- > > Key: FOP-3176 > URL: https://issues.apache.org/jira/browse/FOP-3176 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > Attachments: fop.xconf, simple.fo > > > test.fo -c fop.xconf out.pdf > Open PDF in acrobat, no error is displayed after running accessibility check -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3176) Remove unused PDFStructElem
[ https://issues.apache.org/jira/browse/FOP-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3176: --- Attachment: fop.xconf > Remove unused PDFStructElem > --- > > Key: FOP-3176 > URL: https://issues.apache.org/jira/browse/FOP-3176 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, simple.fo > > > test.fo -c fop.xconf out.pdf > Open PDF in acrobat, no error is displayed after running accessibility check -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3176) Remove unused PDFStructElem
[ https://issues.apache.org/jira/browse/FOP-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3176: --- Attachment: simple.fo > Remove unused PDFStructElem > --- > > Key: FOP-3176 > URL: https://issues.apache.org/jira/browse/FOP-3176 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, simple.fo > > > test.fo -c fop.xconf out.pdf > Open PDF in acrobat, no error is displayed after running accessibility check -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3176) Remove unused PDFStructElem
[ https://issues.apache.org/jira/browse/FOP-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3176: --- Description: test.fo -c fop.xconf out.pdf Open PDF in acrobat, no error is displayed after running accessibility check > Remove unused PDFStructElem > --- > > Key: FOP-3176 > URL: https://issues.apache.org/jira/browse/FOP-3176 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > > test.fo -c fop.xconf out.pdf > Open PDF in acrobat, no error is displayed after running accessibility check -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3176) Remove unused PDFStructElem
Simon Steiner created FOP-3176: -- Summary: Remove unused PDFStructElem Key: FOP-3176 URL: https://issues.apache.org/jira/browse/FOP-3176 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-2983) [PATCH] Font auto-detection doesn't work
[ https://issues.apache.org/jira/browse/FOP-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836636#comment-17836636 ] Simon Steiner commented on FOP-2983: assembly.xml changes are here https://github.com/apache/xmlgraphics-fop/commit/cb26fed42b675c576d8f4b69827a32a25e36c5bb > [PATCH] Font auto-detection doesn't work > > > Key: FOP-2983 > URL: https://issues.apache.org/jira/browse/FOP-2983 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.5, 2.6 > Environment: Apache Maven 3.6.0 > Java version: 1.8.0_181, vendor: Oracle Corporation > Default locale: ru_RU, platform encoding: Cp1251 > OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" >Reporter: Sergey Gorbunov >Priority: Critical > Attachments: fonts-auto-detect.patch, image-2024-2-13_11-55-53.png, > image-2024-2-13_11-57-21.png, image-2024-2-13_13-2-57.png, > image-2024-2-13_13-4-5.png > > > When constructing a tree with a configuration, the node for auto-detection is > added to the wrong parent node. As a result, the flag remains with a false. > Detected when trying to convert SVG to PDF with Cyrillic characters. Since > the correct font was not detected automatically, incorrect characters were > displayed after conversion. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FOP-2983) [PATCH] Font auto-detection doesn't work
[ https://issues.apache.org/jira/browse/FOP-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836635#comment-17836635 ] Simon Steiner commented on FOP-2983: Can you add a unit test > [PATCH] Font auto-detection doesn't work > > > Key: FOP-2983 > URL: https://issues.apache.org/jira/browse/FOP-2983 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.5, 2.6 > Environment: Apache Maven 3.6.0 > Java version: 1.8.0_181, vendor: Oracle Corporation > Default locale: ru_RU, platform encoding: Cp1251 > OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" >Reporter: Sergey Gorbunov >Priority: Critical > Attachments: fonts-auto-detect.patch, image-2024-2-13_11-55-53.png, > image-2024-2-13_11-57-21.png, image-2024-2-13_13-2-57.png, > image-2024-2-13_13-4-5.png > > > When constructing a tree with a configuration, the node for auto-detection is > added to the wrong parent node. As a result, the flag remains with a false. > Detected when trying to convert SVG to PDF with Cyrillic characters. Since > the correct font was not detected automatically, incorrect characters were > displayed after conversion. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FOP-3172) image-loading configuration settings are not thread-safe
[ https://issues.apache.org/jira/browse/FOP-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner reassigned FOP-3172: -- Assignee: Simon Steiner > image-loading configuration settings are not thread-safe > > > Key: FOP-3172 > URL: https://issues.apache.org/jira/browse/FOP-3172 > Project: FOP > Issue Type: Bug > Components: image/unqualified >Affects Versions: 2.9 >Reporter: Martin Leitner >Assignee: Simon Steiner >Priority: Major > Attachments: fop_3172.zip > > > As a workaround for FOP-3171 I added an section to the config > and noticed that the settings will take effect on all subsequent renderings > in the same VM, even when they use a different config or none at all. When > running two or more rendering processes with different configs in parallel, > the result will basically be random. > At the very least, this behaviour should be documented and warned about. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-3174) Allow sections which need security permissions to be run when AllPermission denied in caller code
[ https://issues.apache.org/jira/browse/FOP-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3174. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop/commit/64846a5c4ccdf0d900058fef60c2232926dbd6ad > Allow sections which need security permissions to be run when AllPermission > denied in caller code > - > > Key: FOP-3174 > URL: https://issues.apache.org/jira/browse/FOP-3174 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > > See FOP-3038 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3174) Allow sections which need security permissions to be run when AllPermission denied in caller code
Simon Steiner created FOP-3174: -- Summary: Allow sections which need security permissions to be run when AllPermission denied in caller code Key: FOP-3174 URL: https://issues.apache.org/jira/browse/FOP-3174 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3174) Allow sections which need security permissions to be run when AllPermission denied in caller code
[ https://issues.apache.org/jira/browse/FOP-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3174: --- Description: See FOP-3038 > Allow sections which need security permissions to be run when AllPermission > denied in caller code > - > > Key: FOP-3174 > URL: https://issues.apache.org/jira/browse/FOP-3174 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > > See FOP-3038 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FOP-3172) image-loading configuration settings are not thread-safe
[ https://issues.apache.org/jira/browse/FOP-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831870#comment-17831870 ] Simon Steiner commented on FOP-3172: what if you create a fopfactory and pass in your fop.xconf as the 2nd param: FopFactory newInstance(URI baseURI, InputStream confStream) > image-loading configuration settings are not thread-safe > > > Key: FOP-3172 > URL: https://issues.apache.org/jira/browse/FOP-3172 > Project: FOP > Issue Type: Bug > Components: image/unqualified >Affects Versions: 2.9 >Reporter: Martin Leitner >Priority: Major > > As a workaround for FOP-3171 I added an section to the config > and noticed that the settings will take effect on all subsequent renderings > in the same VM, even when they use a different config or none at all. When > running two or more rendering processes with different configs in parallel, > the result will basically be random. > At the very least, this behaviour should be documented and warned about. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FOP-3172) image-loading configuration settings are not thread-safe
[ https://issues.apache.org/jira/browse/FOP-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831718#comment-17831718 ] Simon Steiner commented on FOP-3172: Are you running a different fopfactory per thread, which is required > image-loading configuration settings are not thread-safe > > > Key: FOP-3172 > URL: https://issues.apache.org/jira/browse/FOP-3172 > Project: FOP > Issue Type: Bug > Components: image/unqualified >Affects Versions: 2.9 >Reporter: Martin Leitner >Priority: Major > > As a workaround for FOP-3171 I added an section to the config > and noticed that the settings will take effect on all subsequent renderings > in the same VM, even when they use a different config or none at all. When > running two or more rendering processes with different configs in parallel, > the result will basically be random. > At the very least, this behaviour should be documented and warned about. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FOP-3171) Certain PNG images (grayscale, transparent) produce broken PDF
[ https://issues.apache.org/jira/browse/FOP-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829852#comment-17829852 ] Simon Steiner edited comment on FOP-3171 at 3/22/24 12:11 PM: -- What about adding into the fop.xconf: was (Author: ssteiner1): What about adding into the fop.xconf: > Certain PNG images (grayscale, transparent) produce broken PDF > -- > > Key: FOP-3171 > URL: https://issues.apache.org/jira/browse/FOP-3171 > Project: FOP > Issue Type: Bug > Components: image/png >Affects Versions: 2.8 >Reporter: Martin Leitner >Priority: Major > Attachments: document.fo, fop_2.6_ok.pdf, fop_2.7_ok.pdf, > fop_2.8_nok.pdf, fop_2.9_nok.pdf, number.png > > > Rendering the attached document, which references the also attached image, > produces a broken PDF in version 2.8 and 2.9. Depending on the PDF viewer, > the image is distorted, or is shown with a large black bar at the bottom, or > is shown three times, or is not shown at all. In some viewers, the content > following the image is not shown. > Up until version 2.7 the resulting PDF was fine. Generated PDFs are attached. > The image in question was auto-generated by a customer. If this cannot be > fixed easily, it may help to know what property of the image causes the > problem for finding a workaround. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FOP-3171) Certain PNG images (grayscale, transparent) produce broken PDF
[ https://issues.apache.org/jira/browse/FOP-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829852#comment-17829852 ] Simon Steiner commented on FOP-3171: What about adding into the fop.xconf: > Certain PNG images (grayscale, transparent) produce broken PDF > -- > > Key: FOP-3171 > URL: https://issues.apache.org/jira/browse/FOP-3171 > Project: FOP > Issue Type: Bug > Components: image/png >Affects Versions: 2.8 >Reporter: Martin Leitner >Priority: Major > Attachments: document.fo, fop_2.6_ok.pdf, fop_2.7_ok.pdf, > fop_2.8_nok.pdf, fop_2.9_nok.pdf, number.png > > > Rendering the attached document, which references the also attached image, > produces a broken PDF in version 2.8 and 2.9. Depending on the PDF viewer, > the image is distorted, or is shown with a large black bar at the bottom, or > is shown three times, or is not shown at all. In some viewers, the content > following the image is not shown. > Up until version 2.7 the resulting PDF was fine. Generated PDFs are attached. > The image in question was auto-generated by a customer. If this cannot be > fixed easily, it may help to know what property of the image causes the > problem for finding a workaround. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3135) [PATCH] SVG content is displayed on a single line without spaces
[
https://issues.apache.org/jira/browse/FOP-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner updated FOP-3135:
---
Summary: [PATCH] SVG content is displayed on a single line without
spaces (was: SVG content is displayed on a single line without spaces)
> [PATCH] SVG content is displayed on a single line without spaces
>
>
> Key: FOP-3135
> URL: https://issues.apache.org/jira/browse/FOP-3135
> Project: FOP
> Issue Type: Bug
> Components: image/svg
>Reporter: Julien Lacour
>Assignee: Simon Steiner
>Priority: Minor
> Attachments: MI-Calibri-test.pdf, MI-out-patch.pdf, MI-out.pdf,
> MI-test.fo, MI-tspan.svg, MI.patch, WIP-out.pdf, WIP.patch, svg.patch,
> svgBatik.patch, svgCommons.patch, svgFop.patch, tspan.svg
>
>
> We have found an issue in FOP when transforming PDFs with SVGs containing
> with multiple @x and/or @y attributes values.
> The problem is located in
> org.apache.fop.svg.PDFTextPainter.writeGlyphs(FOPGVTGlyphVector,
> GeneralPath), the positions given by x and y are never used when set.
> A possible fix for this issue is the following:
> {code:java}
> for (int i = 0, n = gv.getNumGlyphs(); i < n; i++) {
> int gc = gv.getGlyphCode(i);
> int[] pa = ((i > dp.length) || (dp[i] == null)) ?
> paZero : dp[i];
> if (gv.getGlyphPosition(i) != null) {
> Point2D gp = gv.getGlyphPosition(i);
> double x= gp.getX() - initialPos.getX();
> double y= -(gp.getY() - initialPos.getY());
> double xd = x - xoLast;
> double yd = y - yoLast;
> textUtil.writeTd(xd, yd);
> textUtil.writeTj((char) gc, true, false);
> xc = x + pa[2];
> yc = y + pa[3];
> xoLast = x;
> yoLast = y;
> } else {
> double xo = xc + pa[0];
> double yo = yc + pa[1];
> double xa = f.getWidth(gc);
> double ya = 0;
> double xd = (xo - xoLast) / 1000f;
> double yd = (yo - yoLast) / 1000f;
>
> textUtil.writeTd(xd, yd);
> textUtil.writeTj((char) gc, true, false);
> xc += xa + pa[2];
> yc += ya + pa[3];
> xoLast = xo;
> yoLast = yo;
> }
> }
> {code}
> I also attached an example for testing, it can be opened in Batik for
> comparison.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FOP-3135) SVG content is displayed on a single line without spaces
[
https://issues.apache.org/jira/browse/FOP-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner reassigned FOP-3135:
--
Assignee: Simon Steiner
> SVG content is displayed on a single line without spaces
>
>
> Key: FOP-3135
> URL: https://issues.apache.org/jira/browse/FOP-3135
> Project: FOP
> Issue Type: Bug
> Components: image/svg
>Reporter: Julien Lacour
>Assignee: Simon Steiner
>Priority: Minor
> Attachments: MI-Calibri-test.pdf, MI-out-patch.pdf, MI-out.pdf,
> MI-test.fo, MI-tspan.svg, MI.patch, WIP-out.pdf, WIP.patch, svg.patch,
> svgBatik.patch, svgCommons.patch, svgFop.patch, tspan.svg
>
>
> We have found an issue in FOP when transforming PDFs with SVGs containing
> with multiple @x and/or @y attributes values.
> The problem is located in
> org.apache.fop.svg.PDFTextPainter.writeGlyphs(FOPGVTGlyphVector,
> GeneralPath), the positions given by x and y are never used when set.
> A possible fix for this issue is the following:
> {code:java}
> for (int i = 0, n = gv.getNumGlyphs(); i < n; i++) {
> int gc = gv.getGlyphCode(i);
> int[] pa = ((i > dp.length) || (dp[i] == null)) ?
> paZero : dp[i];
> if (gv.getGlyphPosition(i) != null) {
> Point2D gp = gv.getGlyphPosition(i);
> double x= gp.getX() - initialPos.getX();
> double y= -(gp.getY() - initialPos.getY());
> double xd = x - xoLast;
> double yd = y - yoLast;
> textUtil.writeTd(xd, yd);
> textUtil.writeTj((char) gc, true, false);
> xc = x + pa[2];
> yc = y + pa[3];
> xoLast = x;
> yoLast = y;
> } else {
> double xo = xc + pa[0];
> double yo = yc + pa[1];
> double xa = f.getWidth(gc);
> double ya = 0;
> double xd = (xo - xoLast) / 1000f;
> double yd = (yo - yoLast) / 1000f;
>
> textUtil.writeTd(xd, yd);
> textUtil.writeTj((char) gc, true, false);
> xc += xa + pa[2];
> yc += ya + pa[3];
> xoLast = xo;
> yoLast = yo;
> }
> }
> {code}
> I also attached an example for testing, it can be opened in Batik for
> comparison.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FOP-3169) Properly label FOP version in PDF document properties
[
https://issues.apache.org/jira/browse/FOP-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner resolved FOP-3169.
Resolution: Duplicate
See FOP-3146
> Properly label FOP version in PDF document properties
> -
>
> Key: FOP-3169
> URL: https://issues.apache.org/jira/browse/FOP-3169
> Project: FOP
> Issue Type: Improvement
>Reporter: Radu Coravu
>Priority: Minor
>
> Using the released FOP 2.9 libraries to produce the PDF.
> I open the PDF in Adobe Reader, I go to Document Properties and it says there:
> {code}
> PDF Producer: Apache FOP Version SVN
> {code}
> Maybe it could write there the actual FOP released version number.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (FOP-3160) split packages within the FOP codebase
[
https://issues.apache.org/jira/browse/FOP-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823590#comment-17823590
]
Simon Steiner edited comment on FOP-3160 at 3/5/24 2:36 PM:
https://github.com/apache/xmlgraphics-fop/commit/d3ef77c7d66c49c84df92d5863dae49beaeca708
https://github.com/apache/xmlgraphics-fop/commit/3133a012c156e91876ad60383f9397d038f474a5
https://github.com/apache/xmlgraphics-fop/commit/de9d1b17e9cb89fb6f239e591d3092d98a251a2f
was (Author: ssteiner1):
https://github.com/apache/xmlgraphics-fop/commit/d3ef77c7d66c49c84df92d5863dae49beaeca708
https://github.com/apache/xmlgraphics-fop/commit/3133a012c156e91876ad60383f9397d038f474a5
> split packages within the FOP codebase
> --
>
> Key: FOP-3160
> URL: https://issues.apache.org/jira/browse/FOP-3160
> Project: FOP
> Issue Type: Improvement
>Reporter: Samael Bate
>Assignee: Simon Steiner
>Priority: Major
> Labels: jpms
>
> whilst taking a look at modularising the project (see: FOP-3159) I found that
> that package names are duplicated across the maven sub-modules.
> For example, both fop-core and fop-utils have _org.apache.fop.util.text._
>
> {code:java}
> [ERROR] the unnamed module reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] the unnamed module reads package org.apache.fop.util.text from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] the unnamed module reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] the unnamed module reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module commons.logging reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module commons.logging reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module commons.logging reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module commons.logging reads package org.apache.fop.util.text from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module batik.awt.util reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module batik.awt.util reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module batik.awt.util reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module batik.awt.util reads package org.apache.fop.util.text from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module qdox reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module qdox reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module qdox reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module qdox reads package org.apache.fop.util.text from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module org.apache.commons.io reads package org.apache.fop.events from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module org.apache.commons.io reads package org.apache.fop.tools from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module org.apache.commons.io reads package org.apache.fop.util from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module org.apache.commons.io reads package org.apache.fop.util.text
> from both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.events from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.tools from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.util from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.util.text
> from both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module ant
[jira] [Resolved] (FOP-3160) split packages within the FOP codebase
[
https://issues.apache.org/jira/browse/FOP-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner resolved FOP-3160.
Fix Version/s: main
Resolution: Fixed
> split packages within the FOP codebase
> --
>
> Key: FOP-3160
> URL: https://issues.apache.org/jira/browse/FOP-3160
> Project: FOP
> Issue Type: Improvement
>Reporter: Samael Bate
>Assignee: Simon Steiner
>Priority: Major
> Labels: jpms
> Fix For: main
>
>
> whilst taking a look at modularising the project (see: FOP-3159) I found that
> that package names are duplicated across the maven sub-modules.
> For example, both fop-core and fop-utils have _org.apache.fop.util.text._
>
> {code:java}
> [ERROR] the unnamed module reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] the unnamed module reads package org.apache.fop.util.text from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] the unnamed module reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] the unnamed module reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module commons.logging reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module commons.logging reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module commons.logging reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module commons.logging reads package org.apache.fop.util.text from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module batik.awt.util reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module batik.awt.util reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module batik.awt.util reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module batik.awt.util reads package org.apache.fop.util.text from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module qdox reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module qdox reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module qdox reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module qdox reads package org.apache.fop.util.text from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module org.apache.commons.io reads package org.apache.fop.events from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module org.apache.commons.io reads package org.apache.fop.tools from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module org.apache.commons.io reads package org.apache.fop.util from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module org.apache.commons.io reads package org.apache.fop.util.text
> from both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.events from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.tools from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.util from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.util.text
> from both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module ant reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module ant reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module ant reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module ant reads package org.apache.fop.util.text from both
>
[jira] [Comment Edited] (FOP-3160) split packages within the FOP codebase
[
https://issues.apache.org/jira/browse/FOP-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823590#comment-17823590
]
Simon Steiner edited comment on FOP-3160 at 3/5/24 1:07 PM:
https://github.com/apache/xmlgraphics-fop/commit/d3ef77c7d66c49c84df92d5863dae49beaeca708
https://github.com/apache/xmlgraphics-fop/commit/3133a012c156e91876ad60383f9397d038f474a5
was (Author: ssteiner1):
https://github.com/apache/xmlgraphics-fop/commit/d3ef77c7d66c49c84df92d5863dae49beaeca708
> split packages within the FOP codebase
> --
>
> Key: FOP-3160
> URL: https://issues.apache.org/jira/browse/FOP-3160
> Project: FOP
> Issue Type: Improvement
>Reporter: Samael Bate
>Assignee: Simon Steiner
>Priority: Major
> Labels: jpms
>
> whilst taking a look at modularising the project (see: FOP-3159) I found that
> that package names are duplicated across the maven sub-modules.
> For example, both fop-core and fop-utils have _org.apache.fop.util.text._
>
> {code:java}
> [ERROR] the unnamed module reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] the unnamed module reads package org.apache.fop.util.text from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] the unnamed module reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] the unnamed module reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module commons.logging reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module commons.logging reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module commons.logging reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module commons.logging reads package org.apache.fop.util.text from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module batik.awt.util reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module batik.awt.util reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module batik.awt.util reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module batik.awt.util reads package org.apache.fop.util.text from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module qdox reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module qdox reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module qdox reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module qdox reads package org.apache.fop.util.text from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module org.apache.commons.io reads package org.apache.fop.events from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module org.apache.commons.io reads package org.apache.fop.tools from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module org.apache.commons.io reads package org.apache.fop.util from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module org.apache.commons.io reads package org.apache.fop.util.text
> from both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.events from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.tools from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.util from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.util.text
> from both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module ant reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module ant reads package org.apache.fop.tools from
[jira] [Commented] (FOP-3160) split packages within the FOP codebase
[
https://issues.apache.org/jira/browse/FOP-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823590#comment-17823590
]
Simon Steiner commented on FOP-3160:
https://github.com/apache/xmlgraphics-fop/commit/d3ef77c7d66c49c84df92d5863dae49beaeca708
> split packages within the FOP codebase
> --
>
> Key: FOP-3160
> URL: https://issues.apache.org/jira/browse/FOP-3160
> Project: FOP
> Issue Type: Improvement
>Reporter: Samael Bate
>Assignee: Simon Steiner
>Priority: Major
> Labels: jpms
>
> whilst taking a look at modularising the project (see: FOP-3159) I found that
> that package names are duplicated across the maven sub-modules.
> For example, both fop-core and fop-utils have _org.apache.fop.util.text._
>
> {code:java}
> [ERROR] the unnamed module reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] the unnamed module reads package org.apache.fop.util.text from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] the unnamed module reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] the unnamed module reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module commons.logging reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module commons.logging reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module commons.logging reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module commons.logging reads package org.apache.fop.util.text from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module batik.awt.util reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module batik.awt.util reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module batik.awt.util reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module batik.awt.util reads package org.apache.fop.util.text from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module qdox reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module qdox reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module qdox reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module qdox reads package org.apache.fop.util.text from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module org.apache.commons.io reads package org.apache.fop.events from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module org.apache.commons.io reads package org.apache.fop.tools from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module org.apache.commons.io reads package org.apache.fop.util from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module org.apache.commons.io reads package org.apache.fop.util.text
> from both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.events from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.tools from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.util from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.util.text
> from both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module ant reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module ant reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module ant reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module ant reads package
[jira] [Assigned] (FOP-3160) split packages within the FOP codebase
[
https://issues.apache.org/jira/browse/FOP-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner reassigned FOP-3160:
--
Assignee: Simon Steiner
> split packages within the FOP codebase
> --
>
> Key: FOP-3160
> URL: https://issues.apache.org/jira/browse/FOP-3160
> Project: FOP
> Issue Type: Improvement
>Reporter: Samael Bate
>Assignee: Simon Steiner
>Priority: Major
> Labels: jpms
>
> whilst taking a look at modularising the project (see: FOP-3159) I found that
> that package names are duplicated across the maven sub-modules.
> For example, both fop-core and fop-utils have _org.apache.fop.util.text._
>
> {code:java}
> [ERROR] the unnamed module reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] the unnamed module reads package org.apache.fop.util.text from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] the unnamed module reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] the unnamed module reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module commons.logging reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module commons.logging reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module commons.logging reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module commons.logging reads package org.apache.fop.util.text from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module batik.awt.util reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module batik.awt.util reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module batik.awt.util reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module batik.awt.util reads package org.apache.fop.util.text from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module qdox reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module qdox reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module qdox reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module qdox reads package org.apache.fop.util.text from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module org.apache.commons.io reads package org.apache.fop.events from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module org.apache.commons.io reads package org.apache.fop.tools from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module org.apache.commons.io reads package org.apache.fop.util from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module org.apache.commons.io reads package org.apache.fop.util.text
> from both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.events from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.tools from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.util from
> both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module xmlgraphics.commons reads package org.apache.fop.util.text
> from both org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module ant reads package org.apache.fop.events from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module ant reads package org.apache.fop.tools from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.events
> [ERROR] module ant reads package org.apache.fop.util from both
> org.apache.xmlgraphics.fop.core and org.apache.xmlgraphics.fop.util
> [ERROR] module ant reads package org.apache.fop.util.text from both
> org.apache.xmlgraphics.fop.core and
[jira] [Resolved] (FOP-3168) Add secure processing for XSL input
[ https://issues.apache.org/jira/browse/FOP-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3168. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop/commit/d96ba9a11710d02716b6f4f6107ebfa9ccec7134 > Add secure processing for XSL input > --- > > Key: FOP-3168 > URL: https://issues.apache.org/jira/browse/FOP-3168 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > > We should use FEATURE_SECURE_PROCESSING feature to secure XSL input -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3168) Add secure processing for XSL input
[ https://issues.apache.org/jira/browse/FOP-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3168: --- Description: We should use FEATURE_SECURE_PROCESSING feature to secure XSL input > Add secure processing for XSL input > --- > > Key: FOP-3168 > URL: https://issues.apache.org/jira/browse/FOP-3168 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > > We should use FEATURE_SECURE_PROCESSING feature to secure XSL input -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3168) Add secure processing for XSL input
Simon Steiner created FOP-3168: -- Summary: Add secure processing for XSL input Key: FOP-3168 URL: https://issues.apache.org/jira/browse/FOP-3168 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-3159) Add JPMS support
[
https://issues.apache.org/jira/browse/FOP-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner resolved FOP-3159.
Fix Version/s: main
Resolution: Fixed
https://github.com/apache/xmlgraphics-fop/commit/ed60079e0064febb68d8c5be690c853f6d83ac4a
> Add JPMS support
>
>
> Key: FOP-3159
> URL: https://issues.apache.org/jira/browse/FOP-3159
> Project: FOP
> Issue Type: Task
>Reporter: Samael Bate
>Assignee: Simon Steiner
>Priority: Major
> Labels: jpms
> Fix For: main
>
>
> There are three potential options for supporting JPMS:
> # Target a JDK above 8 and have module-info.java in each package
> # Publish multi-release jars using latest maven-compiler-plugin with a
> module-info.java in src/main/java9/module-info.java
> # Add Automatic-Module-Name to manifest of published jars
>
> {_}note that for options 1 or 2 the following dependencies should also
> publish jars using module-info{_}:
> * ant
> * batik-awt-util (https://issues.apache.org/jira/browse/BATIK-1362)
> * qdox
> * xmlgraphics-commons (https://issues.apache.org/jira/browse/XGC-127)
> * commons-logging (LOGGING-165, it's worth just ditching commons-logging
> these days. just use slf4j-api)
> * servlet-api-2.2 (just use the newer one)
>
> I personally like option 2 and use that for jars I publish to maven central.
> I can do a PR for each approach but ideally would like to see these other two
> PR's merged in first:
> * [https://github.com/apache/xmlgraphics-fop/pull/74]
> * [https://github.com/apache/xmlgraphics-fop/pull/75]
>
> Based on naming convention used by other Apache projects I suspect the module
> names should be:
> * org.apache.xmlgraphics.fop
> * org.apache.xmlgraphics.fop.core
> * org.apache.xmlgraphics.fop.events
> * org.apache.xmlgraphics.fop.sandbox
> * org.apache.xmlgraphics.fop.transcoder
> * org.apache.xmlgraphics.fop.util
>
> I'm happy to do PR's for any of the 3 options given if someone is willing to
> review & merge.
>
> Due to lack of proper JPMS support in the project dependencies defining
> _Automatic-Module-Name_ in the manifest is the way to go for now.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FOP-3159) Add JPMS support
[
https://issues.apache.org/jira/browse/FOP-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner reassigned FOP-3159:
--
Assignee: Simon Steiner
> Add JPMS support
>
>
> Key: FOP-3159
> URL: https://issues.apache.org/jira/browse/FOP-3159
> Project: FOP
> Issue Type: Task
>Reporter: Samael Bate
>Assignee: Simon Steiner
>Priority: Major
> Labels: jpms
>
> There are three potential options for supporting JPMS:
> # Target a JDK above 8 and have module-info.java in each package
> # Publish multi-release jars using latest maven-compiler-plugin with a
> module-info.java in src/main/java9/module-info.java
> # Add Automatic-Module-Name to manifest of published jars
>
> {_}note that for options 1 or 2 the following dependencies should also
> publish jars using module-info{_}:
> * ant
> * batik-awt-util (https://issues.apache.org/jira/browse/BATIK-1362)
> * qdox
> * xmlgraphics-commons (https://issues.apache.org/jira/browse/XGC-127)
> * commons-logging (LOGGING-165, it's worth just ditching commons-logging
> these days. just use slf4j-api)
> * servlet-api-2.2 (just use the newer one)
>
> I personally like option 2 and use that for jars I publish to maven central.
> I can do a PR for each approach but ideally would like to see these other two
> PR's merged in first:
> * [https://github.com/apache/xmlgraphics-fop/pull/74]
> * [https://github.com/apache/xmlgraphics-fop/pull/75]
>
> Based on naming convention used by other Apache projects I suspect the module
> names should be:
> * org.apache.xmlgraphics.fop
> * org.apache.xmlgraphics.fop.core
> * org.apache.xmlgraphics.fop.events
> * org.apache.xmlgraphics.fop.sandbox
> * org.apache.xmlgraphics.fop.transcoder
> * org.apache.xmlgraphics.fop.util
>
> I'm happy to do PR's for any of the 3 options given if someone is willing to
> review & merge.
>
> Due to lack of proper JPMS support in the project dependencies defining
> _Automatic-Module-Name_ in the manifest is the way to go for now.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FOP-3166) Add option to sign PDF
[ https://issues.apache.org/jira/browse/FOP-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3166. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop/commit/08d676ebd139a827fc2e6756d1ab542bce1a17b7 > Add option to sign PDF > -- > > Key: FOP-3166 > URL: https://issues.apache.org/jira/browse/FOP-3166 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > Attachments: fop.xconf, mykeystore.pkcs12, test.fo > > > As a user I want to sign my pdf > Run this cmd: > openssl req -new -newkey rsa:4096 -nodes -keyout my.key -out my.csr > openssl x509 -req -sha256 -days 365 -in my.csr -signkey my.key -out my.pem > cat my.key my.pem > my2.pem > openssl pkcs12 -export -in my2.pem -out mykeystore.pkcs12 -name myAlias > Add to pdf section of fop.xconf: >mykeystore.pkcs12 xxx > > fop test.fo -c fop.xconf out.pdf > In Adobe Reader it should say in side panel: > Document has not been modified since it was certified -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3166) Add option to sign PDF
[ https://issues.apache.org/jira/browse/FOP-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3166: --- Description: As a user I want to sign my pdf Run this cmd: openssl req -new -newkey rsa:4096 -nodes -keyout my.key -out my.csr openssl x509 -req -sha256 -days 365 -in my.csr -signkey my.key -out my.pem cat my.key my.pem > my2.pem openssl pkcs12 -export -in my2.pem -out mykeystore.pkcs12 -name myAlias Add to pdf section of fop.xconf: mykeystore.pkcs12 xxx fop test.fo -c fop.xconf out.pdf In Adobe Reader it should say in side panel: Document has not been modified since it was certified was: As a user I want to sign my pdf Run this cmd: openssl req -new -newkey rsa:4096 -nodes -keyout my.key -out my.csr openssl x509 -req -sha256 -days 365 -in my.csr -signkey my.key -out my.pem cat my.key my.pem > my2.pem openssl pkcs12 -export -in my2.pem -out mykeystore.pkcs12 -name myAlias Add to pdf section of fop.xconf: mykeystore.pkcs12 xxx In Adobe Reader it should say in side panel: Document has not been modified since it was certified > Add option to sign PDF > -- > > Key: FOP-3166 > URL: https://issues.apache.org/jira/browse/FOP-3166 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, mykeystore.pkcs12, test.fo > > > As a user I want to sign my pdf > Run this cmd: > openssl req -new -newkey rsa:4096 -nodes -keyout my.key -out my.csr > openssl x509 -req -sha256 -days 365 -in my.csr -signkey my.key -out my.pem > cat my.key my.pem > my2.pem > openssl pkcs12 -export -in my2.pem -out mykeystore.pkcs12 -name myAlias > Add to pdf section of fop.xconf: >mykeystore.pkcs12 xxx > > fop test.fo -c fop.xconf out.pdf > In Adobe Reader it should say in side panel: > Document has not been modified since it was certified -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3166) Add option to sign PDF
[ https://issues.apache.org/jira/browse/FOP-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3166: --- Attachment: fop.xconf mykeystore.pkcs12 test.fo > Add option to sign PDF > -- > > Key: FOP-3166 > URL: https://issues.apache.org/jira/browse/FOP-3166 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, mykeystore.pkcs12, test.fo > > > As a user I want to sign my pdf > Run this cmd: > openssl req -new -newkey rsa:4096 -nodes -keyout my.key -out my.csr > openssl x509 -req -sha256 -days 365 -in my.csr -signkey my.key -out my.pem > cat my.key my.pem > my2.pem > openssl pkcs12 -export -in my2.pem -out mykeystore.pkcs12 -name myAlias > Add to pdf section of fop.xconf: >mykeystore.pkcs12 xxx > > > In Adobe Reader it should say in side panel: > Document has not been modified since it was certified -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3166) Add option to sign PDF
Simon Steiner created FOP-3166: -- Summary: Add option to sign PDF Key: FOP-3166 URL: https://issues.apache.org/jira/browse/FOP-3166 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner As a user I want to sign my pdf Run this cmd: openssl req -new -newkey rsa:4096 -nodes -keyout my.key -out my.csr openssl x509 -req -sha256 -days 365 -in my.csr -signkey my.key -out my.pem cat my.key my.pem > my2.pem openssl pkcs12 -export -in my2.pem -out mykeystore.pkcs12 -name myAlias Add to pdf section of fop.xconf: mykeystore.pkcs12 xxx In Adobe Reader it should say in side panel: Document has not been modified since it was certified -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FOP-3088) [PATCH] Jar packaging duplicates classes on classpath
[
https://issues.apache.org/jira/browse/FOP-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808662#comment-17808662
]
Simon Steiner commented on FOP-3088:
Did you try the fix on FOP-3146
> [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: 2.9
>
> 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] [Resolved] (FOP-3158) findbugs-maven-plugin should be replaced with spotbugs-maven-plugin
[ https://issues.apache.org/jira/browse/FOP-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3158. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop/commit/eb97ede04e7e9f2af82fb97b2c8894488498a316 > findbugs-maven-plugin should be replaced with spotbugs-maven-plugin > --- > > Key: FOP-3158 > URL: https://issues.apache.org/jira/browse/FOP-3158 > Project: FOP > Issue Type: Task >Reporter: Samael Bate >Assignee: Simon Steiner >Priority: Major > Fix For: main > > > The findbugs-maven-plugin used in Apache FOP project is dead and should be > replaced by > spotbugs-maven-plugin which is actively maintained > > https://spotbugs.readthedocs.io/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FOP-3158) findbugs-maven-plugin should be replaced with spotbugs-maven-plugin
[ https://issues.apache.org/jira/browse/FOP-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17808151#comment-17808151 ] Simon Steiner commented on FOP-3158: https://github.com/apache/xmlgraphics-fop-pdf-images/commit/d50e777557959a8d64cc4a71bc2dd844f7aee779 > findbugs-maven-plugin should be replaced with spotbugs-maven-plugin > --- > > Key: FOP-3158 > URL: https://issues.apache.org/jira/browse/FOP-3158 > Project: FOP > Issue Type: Task >Reporter: Samael Bate >Assignee: Simon Steiner >Priority: Major > > The findbugs-maven-plugin used in Apache FOP project is dead and should be > replaced by > spotbugs-maven-plugin which is actively maintained > > https://spotbugs.readthedocs.io/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FOP-3158) findbugs-maven-plugin should be replaced with spotbugs-maven-plugin
[ https://issues.apache.org/jira/browse/FOP-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner reassigned FOP-3158: -- Assignee: Simon Steiner > findbugs-maven-plugin should be replaced with spotbugs-maven-plugin > --- > > Key: FOP-3158 > URL: https://issues.apache.org/jira/browse/FOP-3158 > Project: FOP > Issue Type: Task >Reporter: Samael Bate >Assignee: Simon Steiner >Priority: Major > > The findbugs-maven-plugin used in Apache FOP project is dead and should be > replaced by > spotbugs-maven-plugin which is actively maintained > > https://spotbugs.readthedocs.io/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-3157) PCL fonts are printed as numbers and punctuation
[ https://issues.apache.org/jira/browse/FOP-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3157. Resolution: Cannot Reproduce > PCL fonts are printed as numbers and punctuation > > > Key: FOP-3157 > URL: https://issues.apache.org/jira/browse/FOP-3157 > Project: FOP > Issue Type: Bug >Affects Versions: 2.9 >Reporter: Maria >Priority: Major > Attachments: TestPclEmbededFont.fo, TestPclEmbededFont.pcl, > embeddFontOneLine-1.fo, embeddFontOneLine.fo, > embeddFontOneLineSimpleProject-1.pcl, embeddFontOneLineSimpleProject.pcl, > fop.xconf, image-2023-11-01-18-58-56-405.png, > image-2023-11-01-18-59-28-380.png, image-2023-11-01-19-01-44-174.png, > image-2023-11-01-19-05-44-582.png, image-2023-11-01-19-07-21-317.png, > image-2023-11-02-19-36-16-242.png, image-2023-11-02-19-37-25-203.png, > image-2023-11-02-19-38-00-072.png, image-2023-11-02-19-39-17-431.png, > image-2023-11-02-19-40-14-808.png, image-2023-11-09-11-39-34-302.png, > image-2023-11-09-11-41-17-089.png, printedTestEmbededPclFont.png > > > Hello, > > Can you, please, help with embedded fonts in PCL. > > Produced with Apache fop 2.9 (embedded in app) a PCL file with embedded fonts. > When printed on my HP Laser jet P2055dn, all symbols are represented with > numbers and punctuation. > In Red Titan it is almost well represented - it has most of the symbols: > !image-2023-11-01-18-59-28-380.png|width=667,height=226! > > And Fonts are in the document: > !image-2023-11-01-19-01-44-174.png|width=655,height=141! > > However, in PCL Paraphernalia (print analysis tool), symbols are represented > as > |90af|Data| |3#4+ 5#4+
[jira] [Resolved] (FOP-3164) [PATCH] Footnote anchor within fo:basic-link not navigating to corresponding footnote
[
https://issues.apache.org/jira/browse/FOP-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner resolved FOP-3164.
Fix Version/s: main
Resolution: Fixed
https://github.com/apache/xmlgraphics-fop/commit/bfc5d5277a18eb447c4bd2f71d336e05c278d2bf
> [PATCH] Footnote anchor within fo:basic-link not navigating to corresponding
> footnote
> -
>
> Key: FOP-3164
> URL: https://issues.apache.org/jira/browse/FOP-3164
> Project: FOP
> Issue Type: Bug
>Affects Versions: 2.8, 2.9
>Reporter: Raman Katsora
>Assignee: Simon Steiner
>Priority: Major
> Fix For: main
>
> Attachments: fop.patch, npe.pdf, test.fo, test.pdf
>
>
> When a footnote anchor is placed within the {{}} element, the
> expected behavior of navigating to the corresponding footnote upon clicking
> is not observed. Instead, the click action directs the user to follow the
> link associated with the {{}} element, rather than
> transitioning to the targeted footnote.
> *Actual Behavior:*
> Clicking on the footnote anchor redirects users to follow the link associated
> with .
> *Expected Behavior:*
> Clicking on the footnote anchor transitions users to the corresponding
> footnote.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FOP-3164) [PATCH] Footnote anchor within fo:basic-link not navigating to corresponding footnote
[
https://issues.apache.org/jira/browse/FOP-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner reassigned FOP-3164:
--
Assignee: Simon Steiner
> [PATCH] Footnote anchor within fo:basic-link not navigating to corresponding
> footnote
> -
>
> Key: FOP-3164
> URL: https://issues.apache.org/jira/browse/FOP-3164
> Project: FOP
> Issue Type: Bug
>Affects Versions: 2.8, 2.9
>Reporter: Raman Katsora
>Assignee: Simon Steiner
>Priority: Major
> Attachments: fop.patch, npe.pdf, test.fo, test.pdf
>
>
> When a footnote anchor is placed within the {{}} element, the
> expected behavior of navigating to the corresponding footnote upon clicking
> is not observed. Instead, the click action directs the user to follow the
> link associated with the {{}} element, rather than
> transitioning to the targeted footnote.
> *Actual Behavior:*
> Clicking on the footnote anchor redirects users to follow the link associated
> with .
> *Expected Behavior:*
> Clicking on the footnote anchor transitions users to the corresponding
> footnote.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FOP-3144) [PATCH] Is it possible to create a PDF which is both PDF/A and PDF/UA compliant?
[
https://issues.apache.org/jira/browse/FOP-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner resolved FOP-3144.
Fix Version/s: main
Resolution: Fixed
https://github.com/apache/xmlgraphics-commons/commit/241423baf2659ad1e2ad6b702631486f99de751c
https://github.com/apache/xmlgraphics-fop/commit/5e0759650d0176109954a9152ffb70494848c985
> [PATCH] Is it possible to create a PDF which is both PDF/A and PDF/UA
> compliant?
>
>
> Key: FOP-3144
> URL: https://issues.apache.org/jira/browse/FOP-3144
> Project: FOP
> Issue Type: Improvement
> Components: renderer/pdf
>Affects Versions: 2.8
>Reporter: Matteo Franci
>Assignee: Simon Steiner
>Priority: Major
> Fix For: main
>
> Attachments: commons.patch, fonts.fo, fop.patch, pdfFop.xconf,
> pdfUaFonts.pdf
>
>
> I would like to create a PDF which have both a PDF/A and PDF/UA profile
> active.
> It seems validators do not accept the generated property :
> {code:java}
> http://www.aiim.org/pdfua/ns/id/;
> rdf:about="">
> 1
> {code}
> So maybe the issue is not with FOP but with the compatibility of the two
> standards or with the validators.
> Do you have any clues about it?
> I tried a few configurations, for example :
>
> {code:java}
>
> PDF/UA-1
> PDF/A-1a
> 1.4
> ...
>
> {code}
> Or
> {code:java}
>
> PDF/UA-1
> PDF/A-2a
> 1.7
> ...
>
> {code}
> The PDF/UA validation succeds (I tried [https://check.axes4.com/en/]),
> but the PDF/A validation fails (I tried adobe and
> [https://avepdf.com/en/pdfa-validation]
> [),|https://avepdf.com/en/pdfa-validation] with this error :
>
> {color:#ff}XMP property pdfuaid:part not defined in current schema.{color}
>
> Thanks in advance.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FOP-3144) [PATCH] Is it possible to create a PDF which is both PDF/A and PDF/UA compliant?
[
https://issues.apache.org/jira/browse/FOP-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner reassigned FOP-3144:
--
Assignee: Simon Steiner
> [PATCH] Is it possible to create a PDF which is both PDF/A and PDF/UA
> compliant?
>
>
> Key: FOP-3144
> URL: https://issues.apache.org/jira/browse/FOP-3144
> Project: FOP
> Issue Type: Improvement
> Components: renderer/pdf
>Affects Versions: 2.8
>Reporter: Matteo Franci
>Assignee: Simon Steiner
>Priority: Major
> Attachments: commons.patch, fonts.fo, fop.patch, pdfFop.xconf,
> pdfUaFonts.pdf
>
>
> I would like to create a PDF which have both a PDF/A and PDF/UA profile
> active.
> It seems validators do not accept the generated property :
> {code:java}
> http://www.aiim.org/pdfua/ns/id/;
> rdf:about="">
> 1
> {code}
> So maybe the issue is not with FOP but with the compatibility of the two
> standards or with the validators.
> Do you have any clues about it?
> I tried a few configurations, for example :
>
> {code:java}
>
> PDF/UA-1
> PDF/A-1a
> 1.4
> ...
>
> {code}
> Or
> {code:java}
>
> PDF/UA-1
> PDF/A-2a
> 1.7
> ...
>
> {code}
> The PDF/UA validation succeds (I tried [https://check.axes4.com/en/]),
> but the PDF/A validation fails (I tried adobe and
> [https://avepdf.com/en/pdfa-validation]
> [),|https://avepdf.com/en/pdfa-validation] with this error :
>
> {color:#ff}XMP property pdfuaid:part not defined in current schema.{color}
>
> Thanks in advance.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (FOP-2764) [PATCH] footnote-body ignores rl-tb writing mode
[ https://issues.apache.org/jira/browse/FOP-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-2764. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop/commit/01e520466cb43fb5e152c2faed5a47adac0c8f9c > [PATCH] footnote-body ignores rl-tb writing mode > > > Key: FOP-2764 > URL: https://issues.apache.org/jira/browse/FOP-2764 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.2 >Reporter: schwitin >Assignee: Simon Steiner >Priority: Major > Labels: arabic, footnote, rtl > Fix For: main > > Attachments: rightLeft.fo, rightLeft.patch, rightLeft.pdf, > rtl-footnote-test.fo, rtl-footnote-test.pdf > > > Arabic text does not display properly when it is placed in the footnote-body > element. > Related to FOP-2043 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FOP-2764) [PATCH] footnote-body ignores rl-tb writing mode
[ https://issues.apache.org/jira/browse/FOP-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner reassigned FOP-2764: -- Assignee: Simon Steiner > [PATCH] footnote-body ignores rl-tb writing mode > > > Key: FOP-2764 > URL: https://issues.apache.org/jira/browse/FOP-2764 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.2 >Reporter: schwitin >Assignee: Simon Steiner >Priority: Major > Labels: arabic, footnote, rtl > Attachments: rightLeft.fo, rightLeft.patch, rightLeft.pdf, > rtl-footnote-test.fo, rtl-footnote-test.pdf > > > Arabic text does not display properly when it is placed in the footnote-body > element. > Related to FOP-2043 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-2887) java.lang.NullPointerException with "" at org.apache.fop.layoutmgr.PageBreaker.redoLayout(PageBreaker.java:453)
[
https://issues.apache.org/jira/browse/FOP-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner resolved FOP-2887.
Resolution: Cannot Reproduce
> java.lang.NullPointerException with "" at
> org.apache.fop.layoutmgr.PageBreaker.redoLayout(PageBreaker.java:453)
> -
>
> Key: FOP-2887
> URL: https://issues.apache.org/jira/browse/FOP-2887
> Project: FOP
> Issue Type: Bug
>Affects Versions: 2.4
> Environment: openSUSE Tumbleweed x64
>Reporter: Szőts Ákos
>Priority: Major
> Attachments: topic.fo
>
>
> The following code snippet (also attached) causes FOP 2.4 to throw a
> NullPointerException during page layouting.
> I tried to create a minimal reproducible example so anything you'd remove
> semantically correctly will cause the snippet to compile properly.
> {code:xml}
>
> http://www.w3.org/1999/XSL/Format;>
>
>
>
>
>
>
>
>
>
> master-reference="body-last" page-position="last"/>
> master-reference="body-odd"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Exception thrown:
> {code:java}
> SEVERE: Exception
> org.apache.fop.apps.FOPException: java.lang.NullPointerException
> java.lang.NullPointerException
> 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: java.lang.NullPointerException
> at
> org.apache.fop.layoutmgr.PageBreaker.redoLayout(PageBreaker.java:453)
> at org.apache.fop.layoutmgr.PageBreaker.doPhase3(PageBreaker.java:333)
> at
> org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:458)
> at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:112)
> at
> org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:143)
> at
> org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267)
> at
> org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:139)
> at
> org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:362)
> at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:190)
> at
> org.apache.xalan.transformer.TransformerIdentityImpl.endElement(TransformerIdentityImpl.java:1102)
> at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
> Source)
> at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
> Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
> Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
> Source)
> at
> org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:485)
> at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:293)
> ... 3 more
> -
> java.lang.NullPointerException
> at
> org.apache.fop.layoutmgr.PageBreaker.redoLayout(PageBreaker.java:453)
> at org.apache.fop.layoutmgr.PageBreaker.doPhase3(PageBreaker.java:333)
> at
> org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:458)
> at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:112)
> at
> org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:143)
> at
> org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267)
> at
> org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:139)
> at
> org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:362)
> at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:190)
> at
> org.apache.xalan.transformer.TransformerIdentityImpl.endElement(TransformerIdentityImpl.java:1102)
> at
[jira] [Resolved] (FOP-2761) java.lang.ArrayIndexOutOfBoundsException - While Processing URDU (RTL) Contents
[ https://issues.apache.org/jira/browse/FOP-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-2761. Resolution: Cannot Reproduce > java.lang.ArrayIndexOutOfBoundsException - While Processing URDU (RTL) > Contents > --- > > Key: FOP-2761 > URL: https://issues.apache.org/jira/browse/FOP-2761 > Project: FOP > Issue Type: Bug > Components: fo/block >Affects Versions: 2.2 > Environment: I have tested it on Mac OS & Windows 10 >Reporter: Muhammad Shakeel >Priority: Major > Attachments: CommandWithErrorLogMessages.txt, Jameel Noori > Nastaleeq.7z, Sample-UrduContents.fo, fop.xconf > > > Hi, > I am getting "java.lang.ArrayIndexOutOfBoundsException" while I am trying to > process the XSL-FO containing Urdu Language text which is RTL and close to an > Arabic Language. > I have tested the same XSL-FO with Antenna House Formatter (Evaluation > Version) and I am not getting this exception when I use that formatter. > I have attached : > 1. Download the .TTF from http://www.urdujahan.com/font.html > 2. The error logs file with the command I have used > 3. XSL-FO file containing the contents I am having issue with > 4. FOP.XCONF File > Please note that I have "Remarked" the contents which is causing the issue. > Please un-comment the remarked contents and checkout the issue. > I hope you review this reported Bug and share your findings with the issue > soon. > NOTE: I am at the moment experiencing issue to upload the .TTF on JIRA that's > why I have shared the download link. > Thank you, > Kind Regards, > Mumammad Shakeel -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-3163) Optimise performance of PNG with alpha using raw loader
[ https://issues.apache.org/jira/browse/FOP-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3163. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop/commit/23e173b7e6e095c15ac2384e462abbc4281f3e32 > Optimise performance of PNG with alpha using raw loader > --- > > Key: FOP-3163 > URL: https://issues.apache.org/jira/browse/FOP-3163 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > Attachments: fop.xconf > > > Add a png with alpha to a test.fo > fop test.fo out.pdf -c fop.xconf > Time taken is reduced -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3163) Optimise performance of PNG with alpha using raw loader
[ https://issues.apache.org/jira/browse/FOP-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3163: --- Description: Add a png with alpha to a test.fo fop test.fo out.pdf -c fop.xconf Time taken is reduced > Optimise performance of PNG with alpha using raw loader > --- > > Key: FOP-3163 > URL: https://issues.apache.org/jira/browse/FOP-3163 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf > > > Add a png with alpha to a test.fo > fop test.fo out.pdf -c fop.xconf > Time taken is reduced -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3163) Optimise performance of PNG with alpha using raw loader
[ https://issues.apache.org/jira/browse/FOP-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3163: --- Attachment: fop.xconf > Optimise performance of PNG with alpha using raw loader > --- > > Key: FOP-3163 > URL: https://issues.apache.org/jira/browse/FOP-3163 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf > > > Add a png with alpha to a test.fo > fop test.fo out.pdf -c fop.xconf > Time taken is reduced -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3163) Optimise performance of PNG with alpha using raw loader
Simon Steiner created FOP-3163: -- Summary: Optimise performance of PNG with alpha using raw loader Key: FOP-3163 URL: https://issues.apache.org/jira/browse/FOP-3163 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-3162) Missing jars in servlet
[ https://issues.apache.org/jira/browse/FOP-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3162. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop/commit/1cc4244b69d8de060e8fb00e86d4f2a9871e503d > Missing jars in servlet > --- > > Key: FOP-3162 > URL: https://issues.apache.org/jira/browse/FOP-3162 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > > Add fop-servlet.war to tomcat, no classpath error should occur -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3162) Missing jars in servlet
[ https://issues.apache.org/jira/browse/FOP-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3162: --- Description: Add fop-servlet.war to tomcat, no classpath error should occur > Missing jars in servlet > --- > > Key: FOP-3162 > URL: https://issues.apache.org/jira/browse/FOP-3162 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > > Add fop-servlet.war to tomcat, no classpath error should occur -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3162) Missing jars in servlet
Simon Steiner created FOP-3162: -- Summary: Missing jars in servlet Key: FOP-3162 URL: https://issues.apache.org/jira/browse/FOP-3162 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-2851) Adding support for back-of-the-book index
[ https://issues.apache.org/jira/browse/FOP-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789483#comment-17789483 ] Simon Steiner commented on FOP-2851: Jan has created: https://github.com/jan-tosovsky-cz/xmlgraphics-fop/commits/FOP-2851_index > Adding support for back-of-the-book index > - > > Key: FOP-2851 > URL: https://issues.apache.org/jira/browse/FOP-2851 > Project: FOP > Issue Type: Improvement >Reporter: Jan Tošovský >Priority: Major > > Building back-of-the-book index is one of last major features not supported > in FOP. > [https://www.w3.org/TR/xsl/#d0e13293] (formatting objects) > [https://www.w3.org/TR/xsl/#d0e28521] (properties) > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FOP-3161) Table width outside page bounds after change of page width
[ https://issues.apache.org/jira/browse/FOP-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3161. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop/commit/fa9e78ed2ccd890c4eb21f319ea56f9e0545125b > Table width outside page bounds after change of page width > -- > > Key: FOP-3161 > URL: https://issues.apache.org/jira/browse/FOP-3161 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: main > > Attachments: test.fo > > > fop test.fo out.pdf > Table border should be within page bounds -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3161) Table width outside page bounds after change of page width
[ https://issues.apache.org/jira/browse/FOP-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3161: --- Description: fop test.fo out.pdf Table border should be within page bounds was:a > Table width outside page bounds after change of page width > -- > > Key: FOP-3161 > URL: https://issues.apache.org/jira/browse/FOP-3161 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test.fo > > > fop test.fo out.pdf > Table border should be within page bounds -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FOP-3161) Table width outside page bounds after change of page width
[ https://issues.apache.org/jira/browse/FOP-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3161: --- Attachment: test.fo > Table width outside page bounds after change of page width > -- > > Key: FOP-3161 > URL: https://issues.apache.org/jira/browse/FOP-3161 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test.fo > > > a -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FOP-3161) Table width outside page bounds after change of page width
Simon Steiner created FOP-3161: -- Summary: Table width outside page bounds after change of page width Key: FOP-3161 URL: https://issues.apache.org/jira/browse/FOP-3161 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner Attachments: test.fo a -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FOP-3157) PCL fonts are printed as numbers and punctuation
[ https://issues.apache.org/jira/browse/FOP-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17786793#comment-17786793 ] Simon Steiner commented on FOP-3157: What if you print by using the windows lpr command? > PCL fonts are printed as numbers and punctuation > > > Key: FOP-3157 > URL: https://issues.apache.org/jira/browse/FOP-3157 > Project: FOP > Issue Type: Bug >Affects Versions: 2.9 >Reporter: Maria >Priority: Major > Attachments: TestPclEmbededFont.fo, TestPclEmbededFont.pcl, > embeddFontOneLine-1.fo, embeddFontOneLine.fo, > embeddFontOneLineSimpleProject-1.pcl, embeddFontOneLineSimpleProject.pcl, > fop.xconf, image-2023-11-01-18-58-56-405.png, > image-2023-11-01-18-59-28-380.png, image-2023-11-01-19-01-44-174.png, > image-2023-11-01-19-05-44-582.png, image-2023-11-01-19-07-21-317.png, > image-2023-11-02-19-36-16-242.png, image-2023-11-02-19-37-25-203.png, > image-2023-11-02-19-38-00-072.png, image-2023-11-02-19-39-17-431.png, > image-2023-11-02-19-40-14-808.png, image-2023-11-09-11-39-34-302.png, > image-2023-11-09-11-41-17-089.png, printedTestEmbededPclFont.png > > > Hello, > > Can you, please, help with embedded fonts in PCL. > > Produced with Apache fop 2.9 (embedded in app) a PCL file with embedded fonts. > When printed on my HP Laser jet P2055dn, all symbols are represented with > numbers and punctuation. > In Red Titan it is almost well represented - it has most of the symbols: > !image-2023-11-01-18-59-28-380.png|width=667,height=226! > > And Fonts are in the document: > !image-2023-11-01-19-01-44-174.png|width=655,height=141! > > However, in PCL Paraphernalia (print analysis tool), symbols are represented > as > |90af|Data| |3#4+ 5#4+
[jira] [Commented] (FOP-3157) PCL fonts are printed as numbers and punctuation
[ https://issues.apache.org/jira/browse/FOP-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17786769#comment-17786769 ] Simon Steiner commented on FOP-3157: The data in Paraphernalia would not readable as we are using references to glyphs from the ttf font instead of unicode characters > PCL fonts are printed as numbers and punctuation > > > Key: FOP-3157 > URL: https://issues.apache.org/jira/browse/FOP-3157 > Project: FOP > Issue Type: Bug >Affects Versions: 2.9 >Reporter: Maria >Priority: Major > Attachments: TestPclEmbededFont.fo, TestPclEmbededFont.pcl, > embeddFontOneLine-1.fo, embeddFontOneLine.fo, > embeddFontOneLineSimpleProject-1.pcl, embeddFontOneLineSimpleProject.pcl, > fop.xconf, image-2023-11-01-18-58-56-405.png, > image-2023-11-01-18-59-28-380.png, image-2023-11-01-19-01-44-174.png, > image-2023-11-01-19-05-44-582.png, image-2023-11-01-19-07-21-317.png, > image-2023-11-02-19-36-16-242.png, image-2023-11-02-19-37-25-203.png, > image-2023-11-02-19-38-00-072.png, image-2023-11-02-19-39-17-431.png, > image-2023-11-02-19-40-14-808.png, image-2023-11-09-11-39-34-302.png, > image-2023-11-09-11-41-17-089.png, printedTestEmbededPclFont.png > > > Hello, > > Can you, please, help with embedded fonts in PCL. > > Produced with Apache fop 2.9 (embedded in app) a PCL file with embedded fonts. > When printed on my HP Laser jet P2055dn, all symbols are represented with > numbers and punctuation. > In Red Titan it is almost well represented - it has most of the symbols: > !image-2023-11-01-18-59-28-380.png|width=667,height=226! > > And Fonts are in the document: > !image-2023-11-01-19-01-44-174.png|width=655,height=141! > > However, in PCL Paraphernalia (print analysis tool), symbols are represented > as > |90af|Data| |3#4+ 5#4+
[jira] [Commented] (FOP-3157) PCL fonts are printed as numbers and punctuation
[ https://issues.apache.org/jira/browse/FOP-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782277#comment-17782277 ] Simon Steiner commented on FOP-3157: Can we see a fop.xconf file where all font-familys are defined using ttf fonts > PCL fonts are printed as numbers and punctuation > > > Key: FOP-3157 > URL: https://issues.apache.org/jira/browse/FOP-3157 > Project: FOP > Issue Type: Bug >Affects Versions: 2.9 >Reporter: Maria >Priority: Major > Attachments: TestPclEmbededFont.fo, TestPclEmbededFont.pcl, > embeddFontOneLine.fo, embeddFontOneLineSimpleProject.pcl, > image-2023-11-01-18-58-56-405.png, image-2023-11-01-18-59-28-380.png, > image-2023-11-01-19-01-44-174.png, image-2023-11-01-19-05-44-582.png, > image-2023-11-01-19-07-21-317.png, image-2023-11-02-19-36-16-242.png, > image-2023-11-02-19-37-25-203.png, image-2023-11-02-19-38-00-072.png, > image-2023-11-02-19-39-17-431.png, image-2023-11-02-19-40-14-808.png, > printedTestEmbededPclFont.png > > > Hello, > > Can you, please, help with embedded fonts in PCL. > > Produced with Apache fop 2.9 (embedded in app) a PCL file with embedded fonts. > When printed on my HP Laser jet P2055dn, all symbols are represented with > numbers and punctuation. > In Red Titan it is almost well represented - it has most of the symbols: > !image-2023-11-01-18-59-28-380.png|width=667,height=226! > > And Fonts are in the document: > !image-2023-11-01-19-01-44-174.png|width=655,height=141! > > However, in PCL Paraphernalia (print analysis tool), symbols are represented > as > |90af|Data| |3#4+ 5#4+
[jira] [Commented] (FOP-3157) PCL fonts are printed as numbers and punctuation
[ https://issues.apache.org/jira/browse/FOP-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782266#comment-17782266 ] Simon Steiner commented on FOP-3157: Can you try using ttf fonts > PCL fonts are printed as numbers and punctuation > > > Key: FOP-3157 > URL: https://issues.apache.org/jira/browse/FOP-3157 > Project: FOP > Issue Type: Bug >Affects Versions: 2.9 >Reporter: Maria >Priority: Major > Attachments: TestPclEmbededFont.fo, TestPclEmbededFont.pcl, > embeddFontOneLine.fo, embeddFontOneLineSimpleProject.pcl, > image-2023-11-01-18-58-56-405.png, image-2023-11-01-18-59-28-380.png, > image-2023-11-01-19-01-44-174.png, image-2023-11-01-19-05-44-582.png, > image-2023-11-01-19-07-21-317.png, image-2023-11-02-19-36-16-242.png, > image-2023-11-02-19-37-25-203.png, image-2023-11-02-19-38-00-072.png, > image-2023-11-02-19-39-17-431.png, image-2023-11-02-19-40-14-808.png, > printedTestEmbededPclFont.png > > > Hello, > > Can you, please, help with embedded fonts in PCL. > > Produced with Apache fop 2.9 (embedded in app) a PCL file with embedded fonts. > When printed on my HP Laser jet P2055dn, all symbols are represented with > numbers and punctuation. > In Red Titan it is almost well represented - it has most of the symbols: > !image-2023-11-01-18-59-28-380.png|width=667,height=226! > > And Fonts are in the document: > !image-2023-11-01-19-01-44-174.png|width=655,height=141! > > However, in PCL Paraphernalia (print analysis tool), symbols are represented > as > |90af|Data| |3#4+ 5#4+
[jira] [Commented] (FOP-3157) PCL fonts are printed as numbers and punctuation
[ https://issues.apache.org/jira/browse/FOP-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782258#comment-17782258 ] Simon Steiner commented on FOP-3157: Can we see the fop.xconf? > PCL fonts are printed as numbers and punctuation > > > Key: FOP-3157 > URL: https://issues.apache.org/jira/browse/FOP-3157 > Project: FOP > Issue Type: Bug >Affects Versions: 2.9 >Reporter: Maria >Priority: Major > Attachments: TestPclEmbededFont.fo, TestPclEmbededFont.pcl, > embeddFontOneLine.fo, embeddFontOneLineSimpleProject.pcl, > image-2023-11-01-18-58-56-405.png, image-2023-11-01-18-59-28-380.png, > image-2023-11-01-19-01-44-174.png, image-2023-11-01-19-05-44-582.png, > image-2023-11-01-19-07-21-317.png, image-2023-11-02-19-36-16-242.png, > image-2023-11-02-19-37-25-203.png, image-2023-11-02-19-38-00-072.png, > image-2023-11-02-19-39-17-431.png, image-2023-11-02-19-40-14-808.png, > printedTestEmbededPclFont.png > > > Hello, > > Can you, please, help with embedded fonts in PCL. > > Produced with Apache fop 2.9 (embedded in app) a PCL file with embedded fonts. > When printed on my HP Laser jet P2055dn, all symbols are represented with > numbers and punctuation. > In Red Titan it is almost well represented - it has most of the symbols: > !image-2023-11-01-18-59-28-380.png|width=667,height=226! > > And Fonts are in the document: > !image-2023-11-01-19-01-44-174.png|width=655,height=141! > > However, in PCL Paraphernalia (print analysis tool), symbols are represented > as > |90af|Data| |3#4+ 5#4+
[jira] [Commented] (FOP-3157) PCL fonts are printed as numbers and punctuation
[ https://issues.apache.org/jira/browse/FOP-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781851#comment-17781851 ] Simon Steiner commented on FOP-3157: Can you try to enable optimize-resources for pcl in fop.xconf and define ttf fonts there also? > PCL fonts are printed as numbers and punctuation > > > Key: FOP-3157 > URL: https://issues.apache.org/jira/browse/FOP-3157 > Project: FOP > Issue Type: Bug >Affects Versions: 2.9 >Reporter: Maria >Priority: Major > Attachments: TestPclEmbededFont.fo, TestPclEmbededFont.pcl, > image-2023-11-01-18-58-56-405.png, image-2023-11-01-18-59-28-380.png, > image-2023-11-01-19-01-44-174.png, image-2023-11-01-19-05-44-582.png, > image-2023-11-01-19-07-21-317.png, printedTestEmbededPclFont.png > > > Hello, > > Can you, please, help with embedded fonts in PCL. > > Produced with Apache fop 2.9 (embedded in app) a PCL file with embedded fonts. > When printed on my HP Laser jet P2055dn, all symbols are represented with > numbers and punctuation. > In Red Titan it is almost well represented - it has most of the symbols: > !image-2023-11-01-18-59-28-380.png|width=667,height=226! > > And Fonts are in the document: > !image-2023-11-01-19-01-44-174.png|width=655,height=141! > > However, in PCL Paraphernalia (print analysis tool), symbols are represented > as > |90af|Data| |3#4+ 5#4+
[jira] [Resolved] (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 resolved FOP-3155. Fix Version/s: main Resolution: Fixed https://github.com/apache/xmlgraphics-fop-pdf-images/commit/8f3e456c57fb353be3af59fed9ca4a703f4370db > 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 > Fix For: main > > Attachments: Adverse_impact_addendum.pdf, fop.xconf, simple.fo > > > fop simple.fo -c fop.xconf out.pdf > Print PDF to OneNote, no error should occur -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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: --- Description: fop simple.fo -c fop.xconf out.pdf Print PDF to OneNote, no error should occur > 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 > > > fop simple.fo -c fop.xconf out.pdf > Print PDF to OneNote, no error should occur -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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)
