[jira] [Updated] (FOP-3046) Blank page when content doesnt fit onto page-position=only
[ https://issues.apache.org/jira/browse/FOP-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3046: --- Attachment: simple.fo > Blank page when content doesnt fit onto page-position=only > -- > > Key: FOP-3046 > URL: https://issues.apache.org/jira/browse/FOP-3046 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: simple.fo > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FOP-3046) Blank page when content doesnt fit onto page-position=only
[ https://issues.apache.org/jira/browse/FOP-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3046: --- Description: fop simple.fo out.pdf There should be no blank page > Blank page when content doesnt fit onto page-position=only > -- > > Key: FOP-3046 > URL: https://issues.apache.org/jira/browse/FOP-3046 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: simple.fo > > > fop simple.fo out.pdf > There should be no blank page -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (FOP-3046) Blank page when content doesnt fit onto page-position=only
Simon Steiner created FOP-3046: -- Summary: Blank page when content doesnt fit onto page-position=only Key: FOP-3046 URL: https://issues.apache.org/jira/browse/FOP-3046 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (FOP-3045) Font weights are rendered wrong
[
https://issues.apache.org/jira/browse/FOP-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17469340#comment-17469340
]
Simon Steiner edited comment on FOP-3045 at 1/5/22, 2:25 PM:
-
Normal way is to define font files in the fop.xconf which have different
weights, fop will select the font file you want and render it
was (Author: ssteiner1):
Normal way if to define font files in the fop.xconf which have different
weights, fop will select the font file you want and render it
> Font weights are rendered wrong
> ---
>
> Key: FOP-3045
> URL: https://issues.apache.org/jira/browse/FOP-3045
> Project: FOP
> Issue Type: Bug
> Components: font/opentype, renderer/pdf
>Affects Versions: 2.6
> Environment: openSUSE Leap 15.3
> fop 2.6
> google-poppins-fonts 4.003-6.3.1
>Reporter: Quang Tran
>Priority: Major
> Attachments: poppins.fo, poppins.pdf
>
>
> The attached reproducer XLST-FO (poppins.fo) has sample text with font
> weights from 100 - 900.
> Although the font-weights 300 and 100 are substituted with the font-weight
> 200 the following font-weight 400 is being rendered much thinner.
> Snippet from output:
> ...
> {{WARNING: Font "Poppins,normal,300" not found. Substituting with
> "Poppins,normal,200".}}
> {{Jan 05, 2022 3:00:31 PM org.apache.fop.apps.FOUserAgent processEvent}}
> {{WARNING: Font "Poppins,normal,100" not found. Substituting with
> "Poppins,normal,200".}}
> {{Jan 05, 2022 3:00:31 PM org.apache.fop.apps.FOUserAgent processEvent}}
> {{WARNING: Font "Poppins,normal,900" not found. Substituting with
> "Poppins,normal,800".}}
> (Also the normal italic seems to be wrong, too. I'm not sure if it's
> correlated to this issue or another.)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (FOP-3045) Font weights are rendered wrong
[
https://issues.apache.org/jira/browse/FOP-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17469340#comment-17469340
]
Simon Steiner commented on FOP-3045:
Normal way if to define font files in the fop.xconf which have different
weights, fop will select the font file you want and render it
> Font weights are rendered wrong
> ---
>
> Key: FOP-3045
> URL: https://issues.apache.org/jira/browse/FOP-3045
> Project: FOP
> Issue Type: Bug
> Components: font/opentype, renderer/pdf
>Affects Versions: 2.6
> Environment: openSUSE Leap 15.3
> fop 2.6
> google-poppins-fonts 4.003-6.3.1
>Reporter: Quang Tran
>Priority: Major
> Attachments: poppins.fo, poppins.pdf
>
>
> The attached reproducer XLST-FO (poppins.fo) has sample text with font
> weights from 100 - 900.
> Although the font-weights 300 and 100 are substituted with the font-weight
> 200 the following font-weight 400 is being rendered much thinner.
> Snippet from output:
> ...
> {{WARNING: Font "Poppins,normal,300" not found. Substituting with
> "Poppins,normal,200".}}
> {{Jan 05, 2022 3:00:31 PM org.apache.fop.apps.FOUserAgent processEvent}}
> {{WARNING: Font "Poppins,normal,100" not found. Substituting with
> "Poppins,normal,200".}}
> {{Jan 05, 2022 3:00:31 PM org.apache.fop.apps.FOUserAgent processEvent}}
> {{WARNING: Font "Poppins,normal,900" not found. Substituting with
> "Poppins,normal,800".}}
> (Also the normal italic seems to be wrong, too. I'm not sure if it's
> correlated to this issue or another.)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (FOP-3044) Transparency in image show as black for PS
[ https://issues.apache.org/jira/browse/FOP-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3044: --- Attachment: fop.xconf sessiondata2.png simple.fo > Transparency in image show as black for PS > -- > > Key: FOP-3044 > URL: https://issues.apache.org/jira/browse/FOP-3044 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, sessiondata2.png, simple.fo > > > fop simple.fo -c fop.xconf -ps out.ps > Output should match input image -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FOP-3044) Transparency in image show as black for PS
[ https://issues.apache.org/jira/browse/FOP-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3044: --- Description: fop simple.fo -c fop.xconf -ps out.ps Output should match input image > Transparency in image show as black for PS > -- > > Key: FOP-3044 > URL: https://issues.apache.org/jira/browse/FOP-3044 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > > fop simple.fo -c fop.xconf -ps out.ps > Output should match input image -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (FOP-3044) Transparency in image show as black for PS
Simon Steiner created FOP-3044: -- Summary: Transparency in image show as black for PS Key: FOP-3044 URL: https://issues.apache.org/jira/browse/FOP-3044 Project: FOP Issue Type: Bug Reporter: Simon Steiner -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (FOP-3044) Transparency in image show as black for PS
[ https://issues.apache.org/jira/browse/FOP-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner reassigned FOP-3044: -- Assignee: Simon Steiner > Transparency in image show as black for PS > -- > > Key: FOP-3044 > URL: https://issues.apache.org/jira/browse/FOP-3044 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (FOP-3043) NPE
[ https://issues.apache.org/jira/browse/FOP-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464612#comment-17464612 ] Simon Steiner commented on FOP-3043: You need to have 1 fopfactory per thread > NPE > --- > > Key: FOP-3043 > URL: https://issues.apache.org/jira/browse/FOP-3043 > Project: FOP > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Gianluca Lenti >Priority: Blocker > Attachments: 20sm2019render_fop.xml, 20sm2019render_fop.xsl, NPE.txt, > pommsa-render-testfop.zip > > > In a Spring Boot application, we get a lot of NPE, with only four REST > clients asking to produce pdf continuosly. In attachment example spring boot > app, stacktrace and input files (issue is indipendent from this test files). > example call to endpoint: > curl -X POST "http://localhost:8080/pom/render/fopUncompressed; -H "accept: > application/pdf" -H "Content-Type: multipart/form-data" -F > "xsl=@20sm2019render_fop.xsl;type=text/xml" -F > "xml=@20sm2019render_fop.xml;type=text/xml" > on windows dev pc, using jmeter, I can reproduce the issue occasionally, last > test with 30 concurrent threads producing 3000 pdf files shows only 2 NPE. > In the openshift production enviroment with less concurrent clients, the > issue is disruptive. > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (FOP-3036) InternaResourceResolver fails on schemes starting with "data"
[
https://issues.apache.org/jira/browse/FOP-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner resolved FOP-3036.
Resolution: Duplicate
> InternaResourceResolver fails on schemes starting with "data"
> -
>
> Key: FOP-3036
> URL: https://issues.apache.org/jira/browse/FOP-3036
> Project: FOP
> Issue Type: Bug
> Components: unqualified
>Affects Versions: 2.6
>Reporter: Michael Kainzbauer
>Priority: Major
>
> org.apache.fop.apps.io.InternalResourceResolver seems to check for "DataURIs"
> in a wrong way:
>
> {{public Resource getResource(String stringUri) throws IOException,
> URISyntaxException {}}
> {{return
> *{color:#ff}s{color}{color:#ff}tringUri.startsWith("data:"){color}* ?
> new Resource(this.resolveDataURI(stringUri)) :
> this.{color:#57d9a3}getResource{color}(cleanURI(stringUri));}}
> {{}}}
> {{public Resource {color:#57d9a3}getResource{color}(URI uri) throws
> IOException {}}
> {{return uri.getScheme() != null &&
> *{color:#ff}uri.getScheme().startsWith("data"){color}* ? new
> Resource(this.resolveDataURI(uri.toASCIIString())) :
> this.resourceResolver.getResource(this.resolveFromBase(uri));}}
> {{}}}
> The first check in Method {{{}public Resource getResource(String
> stringUri){}}}, if the stringUri starts with "data:" is correct: any URIs
> with, an only with, the scheme "data" will be resolved with the
> resolveDataURI method.
> Example:
> * resolving an URI with scheme "data" will be resolved with the
> resolveDataURI method
> * resolving an URI with scheme "datamatrix" will be delegated to {{public
> Resource {color:#57d9a3}getResource{color}(URI uri) method.}}
> * resolving an URI with scheme "foo" will be delegated to {{public Resource
> {color:#57d9a3}getResource{color}(URI uri) method.}}
>
> The second check in {{{}public Resource {color:#57d9a3}getResource{color}(URI
> uri){}}}, if the scheme starts with data is wrong: any URIs with a scheme
> starting with"data" will be resolved with the resolveDataURI method.
> Example:
> * resolving an URI with scheme "data" will be resolved with the
> resolveDataURI method
> * {{resolving an URI with scheme "datamatrix" will be resolved with the
> resolveDataURI method, which is wrong, should be handled by
> this.resourceResolver.getResource(this.resolveFromBase(uri)}}
> * {{resolving an URI with scheme "foo" will be handled by
> this.resourceResolver.getResource(this.resolveFromBase(uri)}}
>
> The second method should be:
> {{public Resource {color:#57d9a3}getResource{color}(URI uri) throws
> IOException {}}
> {{return uri.getScheme() != null {color:#172b4d}&&
> uri.getScheme().{color}{color:#de350b}*equals*{color}{color:#172b4d}("data")
> {color}? new Resource(this.resolveDataURI(uri.toASCIIString())) :
> this.resourceResolver.getResource(this.resolveFromBase(uri));}}
> {{}}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (FOP-3029) not thread safe when outputting jpeg or other image formats
[ https://issues.apache.org/jira/browse/FOP-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3029. Resolution: Not A Problem > not thread safe when outputting jpeg or other image formats > --- > > Key: FOP-3029 > URL: https://issues.apache.org/jira/browse/FOP-3029 > Project: FOP > Issue Type: Bug > Components: image/unqualified >Affects Versions: 2.6 >Reporter: Samael Bate >Priority: Major > > Using Apache FOP in a server side application to render thousands of labels. > Generally the users request PDF format which works fine but we had reports of > malformed content when users requested png or jpeg. Did some local testing > and confirmed that this is indeed an issue with the apache fop library. > Running through our code in an async manner for pdf's works fine but doing > the same for jpeg get's weird results. > Unfortunately I cannot provide the code used but it should be easy to > reproduce locally. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (FOP-3036) InternaResourceResolver fails on schemes starting with "data"
[
https://issues.apache.org/jira/browse/FOP-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455048#comment-17455048
]
Simon Steiner commented on FOP-3036:
Dup of FOP-2973 ?
> InternaResourceResolver fails on schemes starting with "data"
> -
>
> Key: FOP-3036
> URL: https://issues.apache.org/jira/browse/FOP-3036
> Project: FOP
> Issue Type: Bug
> Components: unqualified
>Affects Versions: 2.6
>Reporter: Michael Kainzbauer
>Priority: Major
>
> org.apache.fop.apps.io.InternalResourceResolver seems to check for "DataURIs"
> in a wrong way:
>
> {{public Resource getResource(String stringUri) throws IOException,
> URISyntaxException {}}
> {{return
> *{color:#ff}s{color}{color:#ff}tringUri.startsWith("data:"){color}* ?
> new Resource(this.resolveDataURI(stringUri)) :
> this.{color:#57d9a3}getResource{color}(cleanURI(stringUri));}}
> {{}}}
> {{public Resource {color:#57d9a3}getResource{color}(URI uri) throws
> IOException {}}
> {{return uri.getScheme() != null &&
> *{color:#ff}uri.getScheme().startsWith("data"){color}* ? new
> Resource(this.resolveDataURI(uri.toASCIIString())) :
> this.resourceResolver.getResource(this.resolveFromBase(uri));}}
> {{}}}
> The first check in Method {{{}public Resource getResource(String
> stringUri){}}}, if the stringUri starts with "data:" is correct: any URIs
> with, an only with, the scheme "data" will be resolved with the
> resolveDataURI method.
> Example:
> * resolving an URI with scheme "data" will be resolved with the
> resolveDataURI method
> * resolving an URI with scheme "datamatrix" will be delegated to {{public
> Resource {color:#57d9a3}getResource{color}(URI uri) method.}}
> * resolving an URI with scheme "foo" will be delegated to {{public Resource
> {color:#57d9a3}getResource{color}(URI uri) method.}}
>
> The second check in {{{}public Resource {color:#57d9a3}getResource{color}(URI
> uri){}}}, if the scheme starts with data is wrong: any URIs with a scheme
> starting with"data" will be resolved with the resolveDataURI method.
> Example:
> * resolving an URI with scheme "data" will be resolved with the
> resolveDataURI method
> * {{resolving an URI with scheme "datamatrix" will be resolved with the
> resolveDataURI method, which is wrong, should be handled by
> this.resourceResolver.getResource(this.resolveFromBase(uri)}}
> * {{resolving an URI with scheme "foo" will be handled by
> this.resourceResolver.getResource(this.resolveFromBase(uri)}}
>
> The second method should be:
> {{public Resource {color:#57d9a3}getResource{color}(URI uri) throws
> IOException {}}
> {{return uri.getScheme() != null {color:#172b4d}&&
> uri.getScheme().{color}{color:#de350b}*equals*{color}{color:#172b4d}("data")
> {color}? new Resource(this.resolveDataURI(uri.toASCIIString())) :
> this.resourceResolver.getResource(this.resolveFromBase(uri));}}
> {{}}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (FOP-3039) AFP include-page-overlay missing X and Y via IF
[ https://issues.apache.org/jira/browse/FOP-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3039. Fix Version/s: trunk Resolution: Fixed http://svn.apache.org/viewvc?view=revision=1895653 > AFP include-page-overlay missing X and Y via IF > --- > > Key: FOP-3039 > URL: https://issues.apache.org/jira/browse/FOP-3039 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > Attachments: test.fo > > > fop test.fo -if application/x-afp out.if > fop -ifin out.if -afp out3.afp > Open in AFPLookup, you should see X and Y not equal to 0 in IPO field -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FOP-3039) AFP include-page-overlay missing X and Y via IF
[ https://issues.apache.org/jira/browse/FOP-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3039: --- Description: fop test.fo -if application/x-afp out.if fop -ifin out.if -afp out3.afp Open in AFPLookup, you should see X and Y not equal to 0 in IPO field > AFP include-page-overlay missing X and Y via IF > --- > > Key: FOP-3039 > URL: https://issues.apache.org/jira/browse/FOP-3039 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test.fo > > > fop test.fo -if application/x-afp out.if > fop -ifin out.if -afp out3.afp > Open in AFPLookup, you should see X and Y not equal to 0 in IPO field -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FOP-3039) AFP include-page-overlay missing X and Y via IF
[ https://issues.apache.org/jira/browse/FOP-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3039: --- Attachment: test.fo > AFP include-page-overlay missing X and Y via IF > --- > > Key: FOP-3039 > URL: https://issues.apache.org/jira/browse/FOP-3039 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test.fo > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (FOP-3039) AFP include-page-overlay missing X and Y via IF
Simon Steiner created FOP-3039: -- Summary: AFP include-page-overlay missing X and Y via IF Key: FOP-3039 URL: https://issues.apache.org/jira/browse/FOP-3039 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (FOP-3038) Allow sections which need security permissions to be run when AllPermission denied in caller code
[
https://issues.apache.org/jira/browse/FOP-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner resolved FOP-3038.
Fix Version/s: trunk
Resolution: Fixed
[http://svn.apache.org/viewvc?view=revision=1895651]
http://svn.apache.org/viewvc?view=revision=1895652
> Allow sections which need security permissions to be run when AllPermission
> denied in caller code
> -
>
> Key: FOP-3038
> URL: https://issues.apache.org/jira/browse/FOP-3038
> Project: FOP
> Issue Type: Bug
>Reporter: Simon Steiner
>Assignee: Simon Steiner
>Priority: Major
> Fix For: trunk
>
> Attachments: TestFop.java, jobProcessor.policy
>
>
> {code:java}
>
> javac -cp
> .:/home/foptrunksvn/fop/build/*:/home/foptrunksvn/fop/lib/*:pro-grade.jar
> TestFop.java
> java -Djava.security.manager=net.sourceforge.prograde.sm.ProGradeJSM
> -Djava.security.policy==/home/securityManager/jobProcessor.policy -cp
> pro-grade.jar:.:/home/foptrunksvn/fop/build/*:/home/foptrunksvn/fop/lib/*
> TestFop {code}
>
> No error should occur
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (FOP-3038) Allow sections which need security permissions to be run when AllPermission denied in caller code
[
https://issues.apache.org/jira/browse/FOP-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner updated FOP-3038:
---
Description:
javac -cp
.:/home/foptrunksvn/fop/build/*{*}:/home/foptrunksvn/fop/lib/*{*}:pro-grade.jar
TestFop.java
java -Djava.security.manager=net.sourceforge.prograde.sm.ProGradeJSM
-Djava.security.policy==/home/securityManager/jobProcessor.policy -cp
pro-grade.jar:.:/home/foptrunksvn/fop/build/*{*}:/home/foptrunksvn/fop/lib/*{*}
TestFop
No error should occur
was:
javac -cp
.:/home/foptrunksvn/fop/build/*:/home/foptrunksvn/fop/lib/*:pro-grade.jar
TestFop.java
java -Djava.security.manager=net.sourceforge.prograde.sm.ProGradeJSM
-Djava.security.policy==/home/securityManager/jobProcessor.policy -cp
pro-grade.jar:.:/home/foptrunksvn/fop/build/*:/home/foptrunksvn/fop/lib/*
TestFop
No error should occur
> Allow sections which need security permissions to be run when AllPermission
> denied in caller code
> -
>
> Key: FOP-3038
> URL: https://issues.apache.org/jira/browse/FOP-3038
> Project: FOP
> Issue Type: Bug
>Reporter: Simon Steiner
>Assignee: Simon Steiner
>Priority: Major
> Attachments: TestFop.java, jobProcessor.policy
>
>
> javac -cp
> .:/home/foptrunksvn/fop/build/*{*}:/home/foptrunksvn/fop/lib/*{*}:pro-grade.jar
> TestFop.java
> java -Djava.security.manager=net.sourceforge.prograde.sm.ProGradeJSM
> -Djava.security.policy==/home/securityManager/jobProcessor.policy -cp
> pro-grade.jar:.:/home/foptrunksvn/fop/build/*{*}:/home/foptrunksvn/fop/lib/*{*}
> TestFop
>
> No error should occur
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (FOP-3038) Allow sections which need security permissions to be run when AllPermission denied in caller code
[
https://issues.apache.org/jira/browse/FOP-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner updated FOP-3038:
---
Description:
{code:java}
javac -cp
.:/home/foptrunksvn/fop/build/*:/home/foptrunksvn/fop/lib/*:pro-grade.jar
TestFop.java
java -Djava.security.manager=net.sourceforge.prograde.sm.ProGradeJSM
-Djava.security.policy==/home/securityManager/jobProcessor.policy -cp
pro-grade.jar:.:/home/foptrunksvn/fop/build/*:/home/foptrunksvn/fop/lib/*
TestFop {code}
No error should occur
was:
javac -cp
.:/home/foptrunksvn/fop/build/*{*}:/home/foptrunksvn/fop/lib/*{*}:pro-grade.jar
TestFop.java
java -Djava.security.manager=net.sourceforge.prograde.sm.ProGradeJSM
-Djava.security.policy==/home/securityManager/jobProcessor.policy -cp
pro-grade.jar:.:/home/foptrunksvn/fop/build/*{*}:/home/foptrunksvn/fop/lib/*{*}
TestFop
No error should occur
> Allow sections which need security permissions to be run when AllPermission
> denied in caller code
> -
>
> Key: FOP-3038
> URL: https://issues.apache.org/jira/browse/FOP-3038
> Project: FOP
> Issue Type: Bug
>Reporter: Simon Steiner
>Assignee: Simon Steiner
>Priority: Major
> Attachments: TestFop.java, jobProcessor.policy
>
>
> {code:java}
>
> javac -cp
> .:/home/foptrunksvn/fop/build/*:/home/foptrunksvn/fop/lib/*:pro-grade.jar
> TestFop.java
> java -Djava.security.manager=net.sourceforge.prograde.sm.ProGradeJSM
> -Djava.security.policy==/home/securityManager/jobProcessor.policy -cp
> pro-grade.jar:.:/home/foptrunksvn/fop/build/*:/home/foptrunksvn/fop/lib/*
> TestFop {code}
>
> No error should occur
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (FOP-3038) Allow sections which need security permissions to be run when AllPermission denied in caller code
[ https://issues.apache.org/jira/browse/FOP-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3038: --- Description: javac -cp .:/home/foptrunksvn/fop/build/*:/home/foptrunksvn/fop/lib/*:pro-grade.jar TestFop.java java -Djava.security.manager=net.sourceforge.prograde.sm.ProGradeJSM -Djava.security.policy==/home/securityManager/jobProcessor.policy -cp pro-grade.jar:.:/home/foptrunksvn/fop/build/*:/home/foptrunksvn/fop/lib/* TestFop No error should occur > Allow sections which need security permissions to be run when AllPermission > denied in caller code > - > > Key: FOP-3038 > URL: https://issues.apache.org/jira/browse/FOP-3038 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: TestFop.java, jobProcessor.policy > > > javac -cp > .:/home/foptrunksvn/fop/build/*:/home/foptrunksvn/fop/lib/*:pro-grade.jar > TestFop.java > java -Djava.security.manager=net.sourceforge.prograde.sm.ProGradeJSM > -Djava.security.policy==/home/securityManager/jobProcessor.policy -cp > pro-grade.jar:.:/home/foptrunksvn/fop/build/*:/home/foptrunksvn/fop/lib/* > TestFop > > No error should occur -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FOP-3038) Allow sections which need security permissions to be run when AllPermission denied in caller code
[ https://issues.apache.org/jira/browse/FOP-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3038: --- Attachment: TestFop.java > Allow sections which need security permissions to be run when AllPermission > denied in caller code > - > > Key: FOP-3038 > URL: https://issues.apache.org/jira/browse/FOP-3038 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: TestFop.java, jobProcessor.policy > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (FOP-3038) Allow sections which need security permissions to be run when AllPermission denied in caller code
Simon Steiner created FOP-3038: -- Summary: Allow sections which need security permissions to be run when AllPermission denied in caller code Key: FOP-3038 URL: https://issues.apache.org/jira/browse/FOP-3038 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner Attachments: TestFop.java, jobProcessor.policy -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FOP-3038) Allow sections which need security permissions to be run when AllPermission denied in caller code
[ https://issues.apache.org/jira/browse/FOP-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3038: --- Attachment: jobProcessor.policy > Allow sections which need security permissions to be run when AllPermission > denied in caller code > - > > Key: FOP-3038 > URL: https://issues.apache.org/jira/browse/FOP-3038 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: TestFop.java, jobProcessor.policy > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (FOP-3037) License issue with embedded font
[ https://issues.apache.org/jira/browse/FOP-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3037. Resolution: Not A Problem > License issue with embedded font > > > Key: FOP-3037 > URL: https://issues.apache.org/jira/browse/FOP-3037 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 2.6 >Reporter: Wim >Priority: Major > > We want to use fop 2.6 but the binary and source distributions contain a > closed source font. > There is one file in this package > (fop-2.6/fop/test/resources/fonts/type1/c0419bt_.pfb) that is licensed under > a U.S. Government Restricted Rights license and cannot be distributed. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (FOP-3037) License issue with embedded font
[ https://issues.apache.org/jira/browse/FOP-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17452949#comment-17452949 ] Simon Steiner commented on FOP-3037: The copyright info is here https://github.com/freedesktop/xorg-font-bitstream-type1/blob/master/Copyright > License issue with embedded font > > > Key: FOP-3037 > URL: https://issues.apache.org/jira/browse/FOP-3037 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 2.6 >Reporter: Wim >Priority: Major > > We want to use fop 2.6 but the binary and source distributions contain a > closed source font. > There is one file in this package > (fop-2.6/fop/test/resources/fonts/type1/c0419bt_.pfb) that is licensed under > a U.S. Government Restricted Rights license and cannot be distributed. > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FOP-3028) fopFactoryBuilder.setConfiguration(fopConfig) ignores multiple configuration fields
[ https://issues.apache.org/jira/browse/FOP-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3028: --- Summary: fopFactoryBuilder.setConfiguration(fopConfig) ignores multiple configuration fields (was: fopFactoryBuilder.setConfiguration(fopConfig) ignores mutliple configuration fields) > fopFactoryBuilder.setConfiguration(fopConfig) ignores multiple configuration > fields > --- > > Key: FOP-3028 > URL: https://issues.apache.org/jira/browse/FOP-3028 > Project: FOP > Issue Type: Bug >Affects Versions: 2.3, 2.6 > Environment: Java 8-11, Windows 7-10 >Reporter: Martin Leitner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > > As described in FOP-2524 (which was wrongly marked as Cannot Reproduce), you > can initialize the FopFactoryBuilder and provide a configuration as > InputStream, which works fine. > However, using fopFactoryBuilder.setConfiguration(config); will simply ignore > a number of configuration fields, among them source-resolution, > source-resolution, complex-scripts, accessibility. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (FOP-3028) fopFactoryBuilder.setConfiguration(fopConfig) ignores mutliple configuration fields
[ https://issues.apache.org/jira/browse/FOP-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3028. Fix Version/s: trunk Resolution: Fixed http://svn.apache.org/viewvc?view=revision=1895426 > fopFactoryBuilder.setConfiguration(fopConfig) ignores mutliple configuration > fields > --- > > Key: FOP-3028 > URL: https://issues.apache.org/jira/browse/FOP-3028 > Project: FOP > Issue Type: Bug >Affects Versions: 2.3, 2.6 > Environment: Java 8-11, Windows 7-10 >Reporter: Martin Leitner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > > As described in FOP-2524 (which was wrongly marked as Cannot Reproduce), you > can initialize the FopFactoryBuilder and provide a configuration as > InputStream, which works fine. > However, using fopFactoryBuilder.setConfiguration(config); will simply ignore > a number of configuration fields, among them source-resolution, > source-resolution, complex-scripts, accessibility. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (FOP-3028) fopFactoryBuilder.setConfiguration(fopConfig) ignores mutliple configuration fields
[ https://issues.apache.org/jira/browse/FOP-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner reassigned FOP-3028: -- Assignee: Simon Steiner > fopFactoryBuilder.setConfiguration(fopConfig) ignores mutliple configuration > fields > --- > > Key: FOP-3028 > URL: https://issues.apache.org/jira/browse/FOP-3028 > Project: FOP > Issue Type: Bug >Affects Versions: 2.3, 2.6 > Environment: Java 8-11, Windows 7-10 >Reporter: Martin Leitner >Assignee: Simon Steiner >Priority: Major > > As described in FOP-2524 (which was wrongly marked as Cannot Reproduce), you > can initialize the FopFactoryBuilder and provide a configuration as > InputStream, which works fine. > However, using fopFactoryBuilder.setConfiguration(config); will simply ignore > a number of configuration fields, among them source-resolution, > source-resolution, complex-scripts, accessibility. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FOP-3035) NPE on combination of ZWSP, NBSP and
[
https://issues.apache.org/jira/browse/FOP-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner updated FOP-3035:
---
Summary: NPE on combination of ZWSP, NBSP and (was:
NullPointerException on combination of ZWSP, NBSP and )
> NPE on combination of ZWSP, NBSP and
>
>
> Key: FOP-3035
> URL: https://issues.apache.org/jira/browse/FOP-3035
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.6
> Environment: Linux SLES 11 running on Intel x86_64
>Reporter: Paul Katz
>Priority: Minor
> Attachments: bad.fo, fop-config.xml, fop.log
>
>
> The following line in my XSL:FO reliably causes a NPE when generating a PDF:
>
> {code:java}
> x {code}
> Removing any single element of this line makes the NPE go away:
>
> * The outer
> * {{The Zero-Width Space}}
> * The inner
> * The Non-Breaking Space
> * The "x" text
> (My actual document has more content within the outer ; I just
> removed everything else to provide the minimum content needed to reproduce
> the NPE.)
> The NPE is reported as:
>
> {code:java}
> SEVERE: Exception
> org.apache.fop.apps.FOPException
> 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
> ... {code}
>
> The complete FOP output is attached as fop.log.
> The complete input XSL:F0 is attached as bad.fo. The line of interest is near
> the bottom of the file. I have placed a comment above it listing several
> variations of the line with each element removed one at a time. Any of those
> alternatives prevents the NPE from occurring.
> My command line is:
>
> {noformat}
> fop/fop-2.6/fop/fop -c WD/fop-config.xml -fo bad.fo bad.pdf 2>&1 | tee
> fop.log{noformat}
> My FOP config file is attached as fop-config.xml.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (FOP-2709) Not able to render Bullets in a list while converting from FO to AFP
[ https://issues.apache.org/jira/browse/FOP-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner closed FOP-2709. -- Resolution: Not A Problem > Not able to render Bullets in a list while converting from FO to AFP > > > Key: FOP-2709 > URL: https://issues.apache.org/jira/browse/FOP-2709 > Project: FOP > Issue Type: Bug >Reporter: baldev >Priority: Major > Attachments: fop.xconf, listdemo.afp, sampleFo.fo > > > While converting the fo to afp file bullets are coming as square box or junk > char. Implemented raster font in config file with fonts family Arial, Symbol. > Attached the fo, config file and result afp file. > logs-- > D:\fop-2.2-bin\fop-2.2\fop>fop -c fop.xconf -fo sampleFo.fo -afp listdemo.afp > May 30, 2017 8:02:14 AM org.apache.fop.events.LoggingEventListener > processEvent > INFO: Rendered page #1. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FOP-1798) [PATCH] Empty fo:inline objects with id attribute generate blank line
[ https://issues.apache.org/jira/browse/FOP-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-1798: --- Summary: [PATCH] Empty fo:inline objects with id attribute generate blank line (was: [Patched] Empty fo:inline objects with id attribute generate blank line) > [PATCH] Empty fo:inline objects with id attribute generate blank line > - > > Key: FOP-1798 > URL: https://issues.apache.org/jira/browse/FOP-1798 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 0.95 > Environment: Operating System: All > Platform: PC >Reporter: Dwayne B. > Attachments: h13-623-Exam-Dumps-2019.pdf, inline-test-cases.zip, > patch.diff > > > As per the summary, fo:inline objects with no content and an id attribute > (e.g. ) will render a blank space; this should not > occur. Please see the example test cases and the PDFs generated by Apache FOP > 0.95 that are in the attached zip file. > I am fairly certain this is related to the resolution of this bug: > https://issues.apache.org/bugzilla/show_bug.cgi?id=42748 and this revision: > http://svn.apache.org/viewvc?view=revision=591437 > Thanks. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (FOP-3034) Update PDFBox to 2.0.24
[ https://issues.apache.org/jira/browse/FOP-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3034. Fix Version/s: trunk Resolution: Fixed [http://svn.apache.org/viewvc?view=revision=1894901] http://svn.apache.org/viewvc?view=revision=1894900 > Update PDFBox to 2.0.24 > --- > > Key: FOP-3034 > URL: https://issues.apache.org/jira/browse/FOP-3034 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (FOP-3034) Update PDFBox to 2.0.24
Simon Steiner created FOP-3034: -- Summary: Update PDFBox to 2.0.24 Key: FOP-3034 URL: https://issues.apache.org/jira/browse/FOP-3034 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (FOP-3033) Update PDFBox to 2.0.21
[ https://issues.apache.org/jira/browse/FOP-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3033. Fix Version/s: trunk Resolution: Fixed [http://svn.apache.org/viewvc?view=revision=1894590] http://svn.apache.org/viewvc?view=revision=1894589 > Update PDFBox to 2.0.21 > --- > > Key: FOP-3033 > URL: https://issues.apache.org/jira/browse/FOP-3033 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FOP-3033) Update PDFBox to 2.0.21
Simon Steiner created FOP-3033: -- Summary: Update PDFBox to 2.0.21 Key: FOP-3033 URL: https://issues.apache.org/jira/browse/FOP-3033 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FOP-3032) Allow to embed native PDF in AFP
[ https://issues.apache.org/jira/browse/FOP-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3032. Fix Version/s: trunk Resolution: Fixed [http://svn.apache.org/viewvc?view=revision=1894579] http://svn.apache.org/viewvc?view=revision=1894578 > Allow to embed native PDF in AFP > > > Key: FOP-3032 > URL: https://issues.apache.org/jira/browse/FOP-3032 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > Attachments: fop.xconf, test.fo > > > fop test.fo -c fop.xconf -afp out.afp > > Open AFP in AFPLookup 3 and you should see PDF in Preview pane > Resource Group: Resource: Object Container: Boc: Object Class has: > Registered object type: PDF Single-page Object -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3032) Allow to embed native PDF in AFP
[ https://issues.apache.org/jira/browse/FOP-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3032: --- Attachment: test.fo fop.xconf > Allow to embed native PDF in AFP > > > Key: FOP-3032 > URL: https://issues.apache.org/jira/browse/FOP-3032 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, test.fo > > > fop test.fo -c fop.xconf -afp out.afp > > Open AFP in AFPLookup 3 and you should see PDF in Preview pane > Resource Group: Resource: Object Container: Boc: Object Class has: > Registered object type: PDF Single-page Object -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3032) Allow to embed native PDF in AFP
[ https://issues.apache.org/jira/browse/FOP-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3032: --- Description: fop test.fo -c fop.xconf -afp out.afp Open AFP in AFPLookup 3 and you should see PDF in Preview pane Resource Group: Resource: Object Container: Boc: Object Class has: Registered object type: PDF Single-page Object was: fop test.fo -c fop.xconf -afp out.afp > Allow to embed native PDF in AFP > > > Key: FOP-3032 > URL: https://issues.apache.org/jira/browse/FOP-3032 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, test.fo > > > fop test.fo -c fop.xconf -afp out.afp > > Open AFP in AFPLookup 3 and you should see PDF in Preview pane > Resource Group: Resource: Object Container: Boc: Object Class has: > Registered object type: PDF Single-page Object -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3032) Allow to embed PDF in AFP
[ https://issues.apache.org/jira/browse/FOP-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3032: --- Description: fop test.fo -c fop.xconf -afp out.afp > Allow to embed PDF in AFP > - > > Key: FOP-3032 > URL: https://issues.apache.org/jira/browse/FOP-3032 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > > fop test.fo -c fop.xconf -afp out.afp > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3032) Allow to embed native PDF in AFP
[ https://issues.apache.org/jira/browse/FOP-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3032: --- Summary: Allow to embed native PDF in AFP (was: Allow to embed PDF in AFP) > Allow to embed native PDF in AFP > > > Key: FOP-3032 > URL: https://issues.apache.org/jira/browse/FOP-3032 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > > fop test.fo -c fop.xconf -afp out.afp > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FOP-3032) Allow to embed PDF in AFP
Simon Steiner created FOP-3032: -- Summary: Allow to embed PDF in AFP Key: FOP-3032 URL: https://issues.apache.org/jira/browse/FOP-3032 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FOP-3031) Add MCF before MDR in AFP
[ https://issues.apache.org/jira/browse/FOP-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3031. Fix Version/s: trunk Resolution: Fixed http://svn.apache.org/viewvc?view=revision=1894576 > Add MCF before MDR in AFP > - > > Key: FOP-3031 > URL: https://issues.apache.org/jira/browse/FOP-3031 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > Attachments: fop.xconf, simple.fo > > > fop simple.fo -afp out3.afp -c fop.xconf > Open in AFPLookup > Open Document: Named Group: Page: AEG: You should see BAG, MCF, MDR, PGD in > that order -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3031) Add MCF before MDR in AFP
[ https://issues.apache.org/jira/browse/FOP-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3031: --- Attachment: simple.fo > Add MCF before MDR in AFP > - > > Key: FOP-3031 > URL: https://issues.apache.org/jira/browse/FOP-3031 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, simple.fo > > > fop simple.fo -afp out3.afp -c fop.xconf > Open in AFPLookup > Open Document: Named Group: Page: AEG: You should see BAG, MCF, MDR, PGD in > that order -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FOP-3031) Add MCF before MDR in AFP
Simon Steiner created FOP-3031: -- Summary: Add MCF before MDR in AFP Key: FOP-3031 URL: https://issues.apache.org/jira/browse/FOP-3031 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner Attachments: fop.xconf, simple.fo -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3031) Add MCF before MDR in AFP
[ https://issues.apache.org/jira/browse/FOP-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3031: --- Attachment: fop.xconf > Add MCF before MDR in AFP > - > > Key: FOP-3031 > URL: https://issues.apache.org/jira/browse/FOP-3031 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, simple.fo > > > fop simple.fo -afp out3.afp -c fop.xconf > Open in AFPLookup > Open Document: Named Group: Page: AEG: You should see BAG, MCF, MDR, PGD in > that order -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3031) Add MCF before MDR in AFP
[ https://issues.apache.org/jira/browse/FOP-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3031: --- Description: fop simple.fo -afp out3.afp -c fop.xconf Open in AFPLookup Open Document: Named Group: Page: AEG: You should see BAG, MCF, MDR, PGD in that order > Add MCF before MDR in AFP > - > > Key: FOP-3031 > URL: https://issues.apache.org/jira/browse/FOP-3031 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, simple.fo > > > fop simple.fo -afp out3.afp -c fop.xconf > Open in AFPLookup > Open Document: Named Group: Page: AEG: You should see BAG, MCF, MDR, PGD in > that order -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FOP-3030) AFP page overlay was written twice
[ https://issues.apache.org/jira/browse/FOP-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3030. Fix Version/s: trunk Resolution: Fixed http://svn.apache.org/viewvc?view=revision=1894575 > AFP page overlay was written twice > -- > > Key: FOP-3030 > URL: https://issues.apache.org/jira/browse/FOP-3030 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > Attachments: test.fo > > > fop test.fo -afp out.afp > Open in WinAFP, you should see once not twice: > Begin Page: Begin Active: Map Page Overlay: O1TSTOVL -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3030) AFP page overlay was written twice
[ https://issues.apache.org/jira/browse/FOP-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3030: --- Attachment: test.fo > AFP page overlay was written twice > -- > > Key: FOP-3030 > URL: https://issues.apache.org/jira/browse/FOP-3030 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test.fo > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3030) AFP page overlay was written twice
[ https://issues.apache.org/jira/browse/FOP-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3030: --- Description: fop test.fo -afp out.afp Open in WinAFP, you should see once not twice: Begin Page: Begin Active: Map Page Overlay: O1TSTOVL > AFP page overlay was written twice > -- > > Key: FOP-3030 > URL: https://issues.apache.org/jira/browse/FOP-3030 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test.fo > > > fop test.fo -afp out.afp > Open in WinAFP, you should see once not twice: > Begin Page: Begin Active: Map Page Overlay: O1TSTOVL -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FOP-3030) AFP page overlay was written twice
Simon Steiner created FOP-3030: -- Summary: AFP page overlay was written twice Key: FOP-3030 URL: https://issues.apache.org/jira/browse/FOP-3030 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FOP-3029) not thread safe when outputting jpeg or other image formats
[ https://issues.apache.org/jira/browse/FOP-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433947#comment-17433947 ] Simon Steiner commented on FOP-3029: The fopfactory isnt thread safe, you can make one per thread > not thread safe when outputting jpeg or other image formats > --- > > Key: FOP-3029 > URL: https://issues.apache.org/jira/browse/FOP-3029 > Project: FOP > Issue Type: Bug > Components: image/unqualified >Affects Versions: 2.6 >Reporter: Samael Bate >Priority: Major > > Using Apache FOP in a server side application to render thousands of labels. > Generally the users request PDF format which works fine but we had reports of > malformed content when users requested png or jpeg. Did some local testing > and confirmed that this is indeed an issue with the apache fop library. > Running through our code in an async manner for pdf's works fine but doing > the same for jpeg get's weird results. > Unfortunately I cannot provide the code used but it should be easy to > reproduce locally. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FOP-1906) Memory leak / Invalid PageViewports stored in IDTracker
[ https://issues.apache.org/jira/browse/FOP-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-1906. Resolution: Cannot Reproduce > Memory leak / Invalid PageViewports stored in IDTracker > --- > > Key: FOP-1906 > URL: https://issues.apache.org/jira/browse/FOP-1906 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 2.5 > Environment: Operating System: All > Platform: All >Reporter: Martin K > Attachments: > 0001-Replace-deleted-PageViewports-in-the-ID-Tracker.patch, > 200-310-Exam-Dumps-NewYear-2019.pdf > > > PageViewports are added to the IDTracker, while content is put into them. > The PageProvider discards PageViewports under some conditions > (discardCacheStartingWith) - the result is, that the ID Tracker has > references to the old PageViewport while the new PageViewport is used for > rendering. > There is a memory leak, as some content is put on the old PageViewport first, > before generating the new PageViewport. The content of the new PageViewport > is freed during rendering - the content of the old PageViewport is not freed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (FOP-1798) Empty fo:inline objects with id attribute generate blank line
[ https://issues.apache.org/jira/browse/FOP-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner reopened FOP-1798: > Empty fo:inline objects with id attribute generate blank line > - > > Key: FOP-1798 > URL: https://issues.apache.org/jira/browse/FOP-1798 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 0.95 > Environment: Operating System: All > Platform: PC >Reporter: Dwayne B. > Attachments: h13-623-Exam-Dumps-2019.pdf, inline-test-cases.zip > > > As per the summary, fo:inline objects with no content and an id attribute > (e.g. ) will render a blank space; this should not > occur. Please see the example test cases and the PDFs generated by Apache FOP > 0.95 that are in the attached zip file. > I am fairly certain this is related to the resolution of this bug: > https://issues.apache.org/bugzilla/show_bug.cgi?id=42748 and this revision: > http://svn.apache.org/viewvc?view=revision=591437 > Thanks. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FOP-1798) Empty fo:inline objects with id attribute generate blank line
[ https://issues.apache.org/jira/browse/FOP-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner closed FOP-1798. -- Resolution: Not A Bug > Empty fo:inline objects with id attribute generate blank line > - > > Key: FOP-1798 > URL: https://issues.apache.org/jira/browse/FOP-1798 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 0.95 > Environment: Operating System: All > Platform: PC >Reporter: Dwayne B. > Attachments: h13-623-Exam-Dumps-2019.pdf, inline-test-cases.zip > > > As per the summary, fo:inline objects with no content and an id attribute > (e.g. ) will render a blank space; this should not > occur. Please see the example test cases and the PDFs generated by Apache FOP > 0.95 that are in the attached zip file. > I am fairly certain this is related to the resolution of this bug: > https://issues.apache.org/bugzilla/show_bug.cgi?id=42748 and this revision: > http://svn.apache.org/viewvc?view=revision=591437 > Thanks. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FOP-2899) Setting a background-color let border vanish
[ https://issues.apache.org/jira/browse/FOP-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner reassigned FOP-2899: -- Assignee: J Frank > Setting a background-color let border vanish > > > Key: FOP-2899 > URL: https://issues.apache.org/jira/browse/FOP-2899 > Project: FOP > Issue Type: Bug > Components: fo/block >Affects Versions: 2.4 >Reporter: Svante Schubert >Assignee: J Frank >Priority: Major > Attachments: UBL-Invoice-2.0-Example_backgroundColor.fo, > UBL-Invoice-2.0-Example_backgroundColor.pdf, > UBL-Invoice-2.0-Example_backgroundColor_indent.fo, > UBL-Invoice-2.0-Example_noBackground.fo, > UBL-Invoice-2.0-Example_noBackground.pdf, > UBL-Invoice-2.0-Example_noBackground_indent.fo, output Border color > black.pdf, output- border color same color as that of background.pdf, > output_Border color Red.pdf, test.fo > > > As soon a background-color is being added to cells the cell border is > vanishing as it seems to use the same color as the background. > I have attached two versions of a document, one with and the other without > background colour as PDF and FO (indent and without indent). > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FOP-2928) [PATCH] PDFDocumentGraphics2D does not clear content on nextPage()
[ https://issues.apache.org/jira/browse/FOP-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-2928. Fix Version/s: trunk Resolution: Fixed http://svn.apache.org/viewvc?view=revision=1894166 > [PATCH] PDFDocumentGraphics2D does not clear content on nextPage() > -- > > Key: FOP-2928 > URL: https://issues.apache.org/jira/browse/FOP-2928 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.2, 2.4 >Reporter: Jürgen Ebert >Assignee: J Frank >Priority: Major > Labels: easyfix > Fix For: trunk > > Attachments: patch-FOP2928-2.diff > > > When switching to a new page using PDFDocumentGraphics2D#nextPage() the > current content is added to the PDF document but it is not cleared. Therefore > the same content will be repeated on the next page. > nextPage() calls closePage() which adds this.getString() to the PDFStream. > this.getString() simply returns the content of currentStream, a StringWriter. > The content of currentStream is never cleared and the reference is never set > to null. Therefore it will be appended to and it will be added again when the > next nextPage() or closePage() or therefore finish() is called. > A work-arround is to manually set the value of currentStream to null using > reflection. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FOP-2973) [PATCH] Cannot use custom schemes starting with "data" in resource resolving
[
https://issues.apache.org/jira/browse/FOP-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner resolved FOP-2973.
Fix Version/s: trunk
Resolution: Fixed
http://svn.apache.org/viewvc?view=revision=1894165
> [PATCH] Cannot use custom schemes starting with "data" in resource resolving
>
>
> Key: FOP-2973
> URL: https://issues.apache.org/jira/browse/FOP-2973
> Project: FOP
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Erik Hofer
>Assignee: J Frank
>Priority: Minor
> Fix For: trunk
>
> Attachments: patch-FOP-2973-3.diff
>
>
> In {{org.apache.fop.apps.io.InternalResourceResolver}} there is the following
> code:
> {code:java}
> public Resource getResource(URI uri) throws IOException {
> if (uri.getScheme() != null && uri.getScheme().startsWith("data")) {
> return new Resource(resolveDataURI(uri.toASCIIString()));
> }
> return resourceResolver.getResource(resolveFromBase(uri));
> }
> {code}
> All URIs with a scheme _starting with_ "data" are treated as a data URI. This
> means schemes like "dataFoo" are not delegated to the {{resourceResolver}}. I
> think this should be {{equals}} instead.
> The string overload works correctly because it includes the colon:
> {code:java}
> public Resource getResource(String stringUri) throws IOException,
> URISyntaxException {
> if (stringUri.startsWith("data:")) {
> return new Resource(resolveDataURI(stringUri));
> }
> return getResource(cleanURI(stringUri));
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (FOP-2943) [PATCH] NPE when fo:block contains inline and character tags and character is a white space
[
https://issues.apache.org/jira/browse/FOP-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner resolved FOP-2943.
Fix Version/s: trunk
Resolution: Fixed
http://svn.apache.org/viewvc?view=revision=1894164
> [PATCH] NPE when fo:block contains inline and character tags and character is
> a white space
> ---
>
> Key: FOP-2943
> URL: https://issues.apache.org/jira/browse/FOP-2943
> Project: FOP
> Issue Type: Bug
> Components: fo/block
>Affects Versions: 2.5
> Environment: debian buster
>Reporter: Attila Soki
>Assignee: J Frank
>Priority: Major
> Fix For: trunk
>
> Attachments: fop-block-npe.fo, patch-FOP-2943.diff
>
>
> The above block causes NullPointerException when written as shown, without
> white spaces between the tags:
> {{block1}}
> adding a space between and solves the problem
> (see testcase: fop-block-npe.fo)
> {{block2
> }}
> {{a non white space fo:character solves the problem too}}
> {{block3 character="-"/>}}
> {{could be related to FOP-2147}}
> The exception:
> java.lang.Exception: Invoke failed:
> [[o:TransformerIdentityImpl]]->;transform((i:Source)[o:StreamSource],
> (i:Result)[o:SAXResult]). Cause: java.lang.NullPointerException VM:
> 1.7.0_45@[http://java.oracle.com/]; at:
> #-33 org.apache.fop.fo.FObj.removeChild(FObj.java:317)
> #-32 org.apache.fop.fo.FObjMixed.removeChild(FObjMixed.java:187)
> #-31
> org.apache.fop.fo.flow.Character$FOCharIterator.remove(Character.java:275)
> #-30
> org.apache.fop.fo.RecursiveCharIterator.remove(RecursiveCharIterator.java:141)
> #-29
> org.apache.fop.fo.XMLWhiteSpaceHandler.handleWhiteSpace(XMLWhiteSpaceHandler.java:321)
> #-28
> org.apache.fop.fo.XMLWhiteSpaceHandler.handleWhiteSpace(XMLWhiteSpaceHandler.java:209)
> #-27 org.apache.fop.fo.FObjMixed.handleWhiteSpaceFor(FObjMixed.java:100)
> #-26 org.apache.fop.fo.FObjMixed.finalizeNode(FObjMixed.java:200)
> #-25 org.apache.fop.fo.FONode.endOfNode(FONode.java:350)
> #-24 org.apache.fop.fo.FObj.endOfNode(FObj.java:222)
> #-23 org.apache.fop.fo.FObjMixed.endOfNode(FObjMixed.java:81)
>
> With FOP version 0.94 works.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FOP-3006) [PATCH] XMP Metadata in created PDF/A-2 documents is not valid
[ https://issues.apache.org/jira/browse/FOP-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3006: --- Fix Version/s: trunk > [PATCH] XMP Metadata in created PDF/A-2 documents is not valid > -- > > Key: FOP-3006 > URL: https://issues.apache.org/jira/browse/FOP-3006 > Project: FOP > Issue Type: Bug >Affects Versions: 2.6, trunk >Reporter: Stefan Berger >Assignee: J Frank >Priority: Major > Fix For: trunk > > Attachments: fop.xconf, fop1.xconf, fop_invalid_metadata.pdf, > patch-FOP-3006.diff, test.fo, test.fo, > veraPDF-tempHTMLReport4387586169468085905.html > > > When you set the "pdf-a-mode" to "PDF/A-2a" and generate a PDF, it will not > pass the validation because and are not valid. > In the case of , it should contain a , and > should contain a . > The offending code is this one: > [https://github.com/apache/xmlgraphics-fop/blob/trunk/fop-core/src/main/java/org/apache/fop/pdf/PDFMetadata.java#L149|https://github.com/apache/xmlgraphics-fop/blob/678d6c0e04fd6a5464012be0241bb771cf9bb506/fop-core/src/main/java/org/apache/fop/pdf/PDFMetadata.java#L149] > By setting compact to true, Bags and Sequences are not created. > Attached you will find a PDF/A-2a file generated by Apache FOP and VeraPDF's > validation results. Other validators also report the same error. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FOP-3006) [PATCH] XMP Metadata in created PDF/A-2 documents is not valid
[ https://issues.apache.org/jira/browse/FOP-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3006. Resolution: Fixed http://svn.apache.org/viewvc?view=revision=1894162 > [PATCH] XMP Metadata in created PDF/A-2 documents is not valid > -- > > Key: FOP-3006 > URL: https://issues.apache.org/jira/browse/FOP-3006 > Project: FOP > Issue Type: Bug >Affects Versions: 2.6, trunk >Reporter: Stefan Berger >Assignee: J Frank >Priority: Major > Attachments: fop.xconf, fop1.xconf, fop_invalid_metadata.pdf, > patch-FOP-3006.diff, test.fo, test.fo, > veraPDF-tempHTMLReport4387586169468085905.html > > > When you set the "pdf-a-mode" to "PDF/A-2a" and generate a PDF, it will not > pass the validation because and are not valid. > In the case of , it should contain a , and > should contain a . > The offending code is this one: > [https://github.com/apache/xmlgraphics-fop/blob/trunk/fop-core/src/main/java/org/apache/fop/pdf/PDFMetadata.java#L149|https://github.com/apache/xmlgraphics-fop/blob/678d6c0e04fd6a5464012be0241bb771cf9bb506/fop-core/src/main/java/org/apache/fop/pdf/PDFMetadata.java#L149] > By setting compact to true, Bags and Sequences are not created. > Attached you will find a PDF/A-2a file generated by Apache FOP and VeraPDF's > validation results. Other validators also report the same error. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FOP-3006) [Patch] XMP Metadata in created PDF/A-2 documents is not valid
[ https://issues.apache.org/jira/browse/FOP-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner reassigned FOP-3006: -- Assignee: J Frank > [Patch] XMP Metadata in created PDF/A-2 documents is not valid > -- > > Key: FOP-3006 > URL: https://issues.apache.org/jira/browse/FOP-3006 > Project: FOP > Issue Type: Bug >Affects Versions: 2.6, trunk >Reporter: Stefan Berger >Assignee: J Frank >Priority: Major > Attachments: fop.xconf, fop1.xconf, fop_invalid_metadata.pdf, > patch-FOP-3006.diff, test.fo, test.fo, > veraPDF-tempHTMLReport4387586169468085905.html > > > When you set the "pdf-a-mode" to "PDF/A-2a" and generate a PDF, it will not > pass the validation because and are not valid. > In the case of , it should contain a , and > should contain a . > The offending code is this one: > [https://github.com/apache/xmlgraphics-fop/blob/trunk/fop-core/src/main/java/org/apache/fop/pdf/PDFMetadata.java#L149|https://github.com/apache/xmlgraphics-fop/blob/678d6c0e04fd6a5464012be0241bb771cf9bb506/fop-core/src/main/java/org/apache/fop/pdf/PDFMetadata.java#L149] > By setting compact to true, Bags and Sequences are not created. > Attached you will find a PDF/A-2a file generated by Apache FOP and VeraPDF's > validation results. Other validators also report the same error. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FOP-3027) Sections of text sometimes lost with span=all multiple columns
[ https://issues.apache.org/jira/browse/FOP-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3027. Fix Version/s: trunk Resolution: Fixed http://svn.apache.org/viewvc?view=revision=1893708 > Sections of text sometimes lost with span=all multiple columns > -- > > Key: FOP-3027 > URL: https://issues.apache.org/jira/browse/FOP-3027 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > Attachments: test.fo > > > fop test.fo out.pdf > No text should be missing from fo -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3027) Sections of text sometimes lost with span=all multiple columns
[ https://issues.apache.org/jira/browse/FOP-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3027: --- Attachment: test.fo > Sections of text sometimes lost with span=all multiple columns > -- > > Key: FOP-3027 > URL: https://issues.apache.org/jira/browse/FOP-3027 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test.fo > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3027) Sections of text sometimes lost with span=all multiple columns
[ https://issues.apache.org/jira/browse/FOP-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3027: --- Description: fop test.fo out.pdf No text should be missing from fo > Sections of text sometimes lost with span=all multiple columns > -- > > Key: FOP-3027 > URL: https://issues.apache.org/jira/browse/FOP-3027 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test.fo > > > fop test.fo out.pdf > No text should be missing from fo -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FOP-3027) Sections of text sometimes lost with span=all multiple columns
Simon Steiner created FOP-3027: -- Summary: Sections of text sometimes lost with span=all multiple columns Key: FOP-3027 URL: https://issues.apache.org/jira/browse/FOP-3027 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-2973) [PATCH] Cannot use custom schemes starting with "data" in resource resolving
[
https://issues.apache.org/jira/browse/FOP-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner updated FOP-2973:
---
Summary: [PATCH] Cannot use custom schemes starting with "data" in resource
resolving (was: [Patch] Cannot use custom schemes starting with "data" in
resource resolving)
> [PATCH] Cannot use custom schemes starting with "data" in resource resolving
>
>
> Key: FOP-2973
> URL: https://issues.apache.org/jira/browse/FOP-2973
> Project: FOP
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Erik Hofer
>Assignee: J Frank
>Priority: Minor
> Attachments: patch-FOP-2973-3.diff
>
>
> In {{org.apache.fop.apps.io.InternalResourceResolver}} there is the following
> code:
> {code:java}
> public Resource getResource(URI uri) throws IOException {
> if (uri.getScheme() != null && uri.getScheme().startsWith("data")) {
> return new Resource(resolveDataURI(uri.toASCIIString()));
> }
> return resourceResolver.getResource(resolveFromBase(uri));
> }
> {code}
> All URIs with a scheme _starting with_ "data" are treated as a data URI. This
> means schemes like "dataFoo" are not delegated to the {{resourceResolver}}. I
> think this should be {{equals}} instead.
> The string overload works correctly because it includes the colon:
> {code:java}
> public Resource getResource(String stringUri) throws IOException,
> URISyntaxException {
> if (stringUri.startsWith("data:")) {
> return new Resource(resolveDataURI(stringUri));
> }
> return getResource(cleanURI(stringUri));
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (FOP-2973) [Patch] Cannot use custom schemes starting with "data" in resource resolving
[
https://issues.apache.org/jira/browse/FOP-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner reassigned FOP-2973:
--
Assignee: J Frank
> [Patch] Cannot use custom schemes starting with "data" in resource resolving
>
>
> Key: FOP-2973
> URL: https://issues.apache.org/jira/browse/FOP-2973
> Project: FOP
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Erik Hofer
>Assignee: J Frank
>Priority: Minor
> Attachments: patch-FOP-2973-3.diff
>
>
> In {{org.apache.fop.apps.io.InternalResourceResolver}} there is the following
> code:
> {code:java}
> public Resource getResource(URI uri) throws IOException {
> if (uri.getScheme() != null && uri.getScheme().startsWith("data")) {
> return new Resource(resolveDataURI(uri.toASCIIString()));
> }
> return resourceResolver.getResource(resolveFromBase(uri));
> }
> {code}
> All URIs with a scheme _starting with_ "data" are treated as a data URI. This
> means schemes like "dataFoo" are not delegated to the {{resourceResolver}}. I
> think this should be {{equals}} instead.
> The string overload works correctly because it includes the colon:
> {code:java}
> public Resource getResource(String stringUri) throws IOException,
> URISyntaxException {
> if (stringUri.startsWith("data:")) {
> return new Resource(resolveDataURI(stringUri));
> }
> return getResource(cleanURI(stringUri));
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (FOP-3026) Fix NPE with empty table header
[ https://issues.apache.org/jira/browse/FOP-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3026. Fix Version/s: trunk Resolution: Fixed http://svn.apache.org/viewvc?view=revision=1892815 > Fix NPE with empty table header > --- > > Key: FOP-3026 > URL: https://issues.apache.org/jira/browse/FOP-3026 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > Attachments: test2.fo > > > fop test2.fo out.pdf -r > No error should occur -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FOP-3026) Fix NPE with empty table header
Simon Steiner created FOP-3026: -- Summary: Fix NPE with empty table header Key: FOP-3026 URL: https://issues.apache.org/jira/browse/FOP-3026 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner Attachments: test2.fo -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3026) Fix NPE with empty table header
[ https://issues.apache.org/jira/browse/FOP-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3026: --- Attachment: test2.fo > Fix NPE with empty table header > --- > > Key: FOP-3026 > URL: https://issues.apache.org/jira/browse/FOP-3026 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test2.fo > > > fop test2.fo out.pdf -r > No error should occur -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3026) Fix NPE with empty table header
[ https://issues.apache.org/jira/browse/FOP-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3026: --- Description: fop test2.fo out.pdf -r No error should occur > Fix NPE with empty table header > --- > > Key: FOP-3026 > URL: https://issues.apache.org/jira/browse/FOP-3026 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test2.fo > > > fop test2.fo out.pdf -r > No error should occur -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FOP-3025) Keep table size on changing ipd which has graphics
[ https://issues.apache.org/jira/browse/FOP-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3025. Fix Version/s: trunk Resolution: Fixed http://svn.apache.org/viewvc?view=revision=1892775 > Keep table size on changing ipd which has graphics > -- > > Key: FOP-3025 > URL: https://issues.apache.org/jira/browse/FOP-3025 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > Attachments: simple.fo > > > fop simple.fo out.pdf > Bar chart should align with text -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3025) Keep table size on changing ipd which has graphics
[ https://issues.apache.org/jira/browse/FOP-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3025: --- Description: fop simple.fo out.pdf Bar chart should align with text > Keep table size on changing ipd which has graphics > -- > > Key: FOP-3025 > URL: https://issues.apache.org/jira/browse/FOP-3025 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: simple.fo > > > fop simple.fo out.pdf > Bar chart should align with text -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FOP-3025) Keep table size on changing ipd which has graphics
Simon Steiner created FOP-3025: -- Summary: Keep table size on changing ipd which has graphics Key: FOP-3025 URL: https://issues.apache.org/jira/browse/FOP-3025 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner Attachments: simple.fo -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3025) Keep table size on changing ipd which has graphics
[ https://issues.apache.org/jira/browse/FOP-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3025: --- Attachment: simple.fo > Keep table size on changing ipd which has graphics > -- > > Key: FOP-3025 > URL: https://issues.apache.org/jira/browse/FOP-3025 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: simple.fo > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FOP-3024) Make sure even number of bytes are output per trn for AFP TTF
[ https://issues.apache.org/jira/browse/FOP-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3024. Fix Version/s: trunk Resolution: Fixed http://svn.apache.org/viewvc?view=revision=1892774 > Make sure even number of bytes are output per trn for AFP TTF > - > > Key: FOP-3024 > URL: https://issues.apache.org/jira/browse/FOP-3024 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > Attachments: fop.xconf, test.fo > > > fop test.fo -c fop.xconf -afp out.afp > Open with afp workbench viewer and no chinese should be shown -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3024) Make sure even number of bytes are output per trn for AFP TTF
[ https://issues.apache.org/jira/browse/FOP-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3024: --- Attachment: test.fo fop.xconf > Make sure even number of bytes are output per trn for AFP TTF > - > > Key: FOP-3024 > URL: https://issues.apache.org/jira/browse/FOP-3024 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, test.fo > > > fop test.fo -c fop.xconf -afp out.afp > Open with afp workbench viewer and no chinese should be shown -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3024) Make sure even number of bytes are output per trn for AFP TTF
[ https://issues.apache.org/jira/browse/FOP-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3024: --- Description: fop test.fo -c fop.xconf -afp out.afp Open with afp workbench viewer and no chinese should be shown > Make sure even number of bytes are output per trn for AFP TTF > - > > Key: FOP-3024 > URL: https://issues.apache.org/jira/browse/FOP-3024 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, test.fo > > > fop test.fo -c fop.xconf -afp out.afp > Open with afp workbench viewer and no chinese should be shown -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FOP-3024) Make sure even number of bytes are output per trn for AFP TTF
Simon Steiner created FOP-3024: -- Summary: Make sure even number of bytes are output per trn for AFP TTF Key: FOP-3024 URL: https://issues.apache.org/jira/browse/FOP-3024 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FOP-2928) [PATCH] PDFDocumentGraphics2D does not clear content on nextPage()
[ https://issues.apache.org/jira/browse/FOP-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner reassigned FOP-2928: -- Assignee: J Frank > [PATCH] PDFDocumentGraphics2D does not clear content on nextPage() > -- > > Key: FOP-2928 > URL: https://issues.apache.org/jira/browse/FOP-2928 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.2, 2.4 >Reporter: Jürgen Ebert >Assignee: J Frank >Priority: Major > Labels: easyfix > Attachments: patch-FOP2928-2.diff > > > When switching to a new page using PDFDocumentGraphics2D#nextPage() the > current content is added to the PDF document but it is not cleared. Therefore > the same content will be repeated on the next page. > nextPage() calls closePage() which adds this.getString() to the PDFStream. > this.getString() simply returns the content of currentStream, a StringWriter. > The content of currentStream is never cleared and the reference is never set > to null. Therefore it will be appended to and it will be added again when the > next nextPage() or closePage() or therefore finish() is called. > A work-arround is to manually set the value of currentStream to null using > reflection. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FOP-2943) NPE when fo:block contains inline and character tags and character is a white space
[
https://issues.apache.org/jira/browse/FOP-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner reassigned FOP-2943:
--
Assignee: J Frank
> NPE when fo:block contains inline and character tags and character is a white
> space
> ---
>
> Key: FOP-2943
> URL: https://issues.apache.org/jira/browse/FOP-2943
> Project: FOP
> Issue Type: Bug
> Components: fo/block
>Affects Versions: 2.5
> Environment: debian buster
>Reporter: Attila Soki
>Assignee: J Frank
>Priority: Major
> Attachments: fop-block-npe.fo
>
>
> The above block causes NullPointerException when written as shown, without
> white spaces between the tags:
> {{block1}}
> adding a space between and solves the problem
> (see testcase: fop-block-npe.fo)
> {{block2
> }}
> {{a non white space fo:character solves the problem too}}
> {{block3 character="-"/>}}
> {{could be related to FOP-2147}}
> The exception:
> java.lang.Exception: Invoke failed:
> [[o:TransformerIdentityImpl]]->;transform((i:Source)[o:StreamSource],
> (i:Result)[o:SAXResult]). Cause: java.lang.NullPointerException VM:
> 1.7.0_45@[http://java.oracle.com/]; at:
> #-33 org.apache.fop.fo.FObj.removeChild(FObj.java:317)
> #-32 org.apache.fop.fo.FObjMixed.removeChild(FObjMixed.java:187)
> #-31
> org.apache.fop.fo.flow.Character$FOCharIterator.remove(Character.java:275)
> #-30
> org.apache.fop.fo.RecursiveCharIterator.remove(RecursiveCharIterator.java:141)
> #-29
> org.apache.fop.fo.XMLWhiteSpaceHandler.handleWhiteSpace(XMLWhiteSpaceHandler.java:321)
> #-28
> org.apache.fop.fo.XMLWhiteSpaceHandler.handleWhiteSpace(XMLWhiteSpaceHandler.java:209)
> #-27 org.apache.fop.fo.FObjMixed.handleWhiteSpaceFor(FObjMixed.java:100)
> #-26 org.apache.fop.fo.FObjMixed.finalizeNode(FObjMixed.java:200)
> #-25 org.apache.fop.fo.FONode.endOfNode(FONode.java:350)
> #-24 org.apache.fop.fo.FObj.endOfNode(FObj.java:222)
> #-23 org.apache.fop.fo.FObjMixed.endOfNode(FObjMixed.java:81)
>
> With FOP version 0.94 works.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (FOP-3021) Property warning when using border-left="thin"
[ https://issues.apache.org/jira/browse/FOP-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3021. Fix Version/s: trunk Resolution: Fixed http://svn.apache.org/viewvc?view=revision=1891499 > Property warning when using border-left="thin" > -- > > Key: FOP-3021 > URL: https://issues.apache.org/jira/browse/FOP-3021 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > Attachments: test.fo > > > fop test.fo out.pdf > You should not see: > WARNING: Invalid property value encountered in border-left="thin" (See > position 21:50) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3021) Property warning when using border-left="thin"
[ https://issues.apache.org/jira/browse/FOP-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3021: --- Description: fop test.fo out.pdf You should not see: WARNING: Invalid property value encountered in border-left="thin" (See position 21:50) > Property warning when using border-left="thin" > -- > > Key: FOP-3021 > URL: https://issues.apache.org/jira/browse/FOP-3021 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test.fo > > > fop test.fo out.pdf > You should not see: > WARNING: Invalid property value encountered in border-left="thin" (See > position 21:50) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3021) Property warning when using border-left="thin"
[ https://issues.apache.org/jira/browse/FOP-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3021: --- Attachment: test.fo > Property warning when using border-left="thin" > -- > > Key: FOP-3021 > URL: https://issues.apache.org/jira/browse/FOP-3021 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test.fo > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FOP-3021) Property warning when using border-left="thin"
Simon Steiner created FOP-3021: -- Summary: Property warning when using border-left="thin" Key: FOP-3021 URL: https://issues.apache.org/jira/browse/FOP-3021 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner Attachments: test.fo -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FOP-3020) Space missing for font merge
[ https://issues.apache.org/jira/browse/FOP-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3020. Fix Version/s: trunk Resolution: Fixed http://svn.apache.org/viewvc?view=revision=1891101 > Space missing for font merge > > > Key: FOP-3020 > URL: https://issues.apache.org/jira/browse/FOP-3020 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > Attachments: fop.xconf, test.fo, ttsubset6.pdf, ttsubset7.pdf > > > fop test.fo -c fop.xconf out.pdf > > Output pdf should match input pdf -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3020) Space missing for font merge
[ https://issues.apache.org/jira/browse/FOP-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3020: --- Description: fop test.fo -c fop.xconf out.pdf Output pdf should match input pdf > Space missing for font merge > > > Key: FOP-3020 > URL: https://issues.apache.org/jira/browse/FOP-3020 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, test.fo, ttsubset6.pdf, ttsubset7.pdf > > > fop test.fo -c fop.xconf out.pdf > > Output pdf should match input pdf -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3020) Space missing for font merge
[ https://issues.apache.org/jira/browse/FOP-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3020: --- Attachment: fop.xconf > Space missing for font merge > > > Key: FOP-3020 > URL: https://issues.apache.org/jira/browse/FOP-3020 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, test.fo, ttsubset6.pdf, ttsubset7.pdf > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3020) Space missing for font merge
[ https://issues.apache.org/jira/browse/FOP-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3020: --- Attachment: ttsubset7.pdf ttsubset6.pdf > Space missing for font merge > > > Key: FOP-3020 > URL: https://issues.apache.org/jira/browse/FOP-3020 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, test.fo, ttsubset6.pdf, ttsubset7.pdf > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FOP-3020) Space missing for font merge
Simon Steiner created FOP-3020: -- Summary: Space missing for font merge Key: FOP-3020 URL: https://issues.apache.org/jira/browse/FOP-3020 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner Attachments: fop.xconf, test.fo, ttsubset6.pdf, ttsubset7.pdf -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3020) Space missing for font merge
[ https://issues.apache.org/jira/browse/FOP-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3020: --- Attachment: test.fo > Space missing for font merge > > > Key: FOP-3020 > URL: https://issues.apache.org/jira/browse/FOP-3020 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: fop.xconf, test.fo, ttsubset6.pdf, ttsubset7.pdf > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FOP-3019) Encryption params from command line are not merged with fop.xconf
[ https://issues.apache.org/jira/browse/FOP-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3019. Fix Version/s: trunk Resolution: Fixed http://svn.apache.org/viewvc?view=revision=1891054 > Encryption params from command line are not merged with fop.xconf > - > > Key: FOP-3019 > URL: https://issues.apache.org/jira/browse/FOP-3019 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > Attachments: fop.xconf, test.fo > > > fop test.fo -c fop.xconf out.pdf -u 123 > Open pdf and it should ask for a password -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3019) Encryption params from command line are not merged with fop.xconf
[ https://issues.apache.org/jira/browse/FOP-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3019: --- Description: fop test.fo -c fop.xconf out.pdf -u 123 Open pdf and it should ask for a password > Encryption params from command line are not merged with fop.xconf > - > > Key: FOP-3019 > URL: https://issues.apache.org/jira/browse/FOP-3019 > 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 -u 123 > Open pdf and it should ask for a password -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3019) Encryption params from command line are not merged with fop.xconf
[ https://issues.apache.org/jira/browse/FOP-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3019: --- Attachment: test.fo fop.xconf > Encryption params from command line are not merged with fop.xconf > - > > Key: FOP-3019 > URL: https://issues.apache.org/jira/browse/FOP-3019 > 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.3.4#803005)
[jira] [Created] (FOP-3019) Encryption params from command line are not merged with fop.xconf
Simon Steiner created FOP-3019: -- Summary: Encryption params from command line are not merged with fop.xconf Key: FOP-3019 URL: https://issues.apache.org/jira/browse/FOP-3019 Project: FOP Issue Type: Bug Reporter: Simon Steiner Assignee: Simon Steiner -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FOP-3018) Allow to disable AFP page group
[ https://issues.apache.org/jira/browse/FOP-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3018. Resolution: Fixed http://svn.apache.org/viewvc?view=revision=1891052 > Allow to disable AFP page group > --- > > Key: FOP-3018 > URL: https://issues.apache.org/jira/browse/FOP-3018 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > Attachments: test.fo > > > fop test.fo -afp out4.afp > > Open with AFPLookup, you should not see Named Group on left side for page 3 > and 4 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3018) Allow to disable AFP page group
[ https://issues.apache.org/jira/browse/FOP-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3018: --- Fix Version/s: trunk > Allow to disable AFP page group > --- > > Key: FOP-3018 > URL: https://issues.apache.org/jira/browse/FOP-3018 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > Attachments: test.fo > > > fop test.fo -afp out4.afp > > Open with AFPLookup, you should not see Named Group on left side for page 3 > and 4 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3018) Allow to disable AFP page group
[ https://issues.apache.org/jira/browse/FOP-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3018: --- Attachment: test.fo > Allow to disable AFP page group > --- > > Key: FOP-3018 > URL: https://issues.apache.org/jira/browse/FOP-3018 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test.fo > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FOP-3018) Allow to disable AFP page group
[ https://issues.apache.org/jira/browse/FOP-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3018: --- Description: fop test.fo -afp out4.afp Open with AFPLookup, you should not see Named Group on left side for page 3 and 4 > Allow to disable AFP page group > --- > > Key: FOP-3018 > URL: https://issues.apache.org/jira/browse/FOP-3018 > Project: FOP > Issue Type: Bug >Reporter: Simon Steiner >Assignee: Simon Steiner >Priority: Major > Attachments: test.fo > > > fop test.fo -afp out4.afp > > Open with AFPLookup, you should not see Named Group on left side for page 3 > and 4 -- This message was sent by Atlassian Jira (v8.3.4#803005)
