[jira] [Commented] (FOP-2930) performance problem in pdf generation

2020-04-15 Thread Chris Bowditch (Jira)


[ 
https://issues.apache.org/jira/browse/FOP-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17084051#comment-17084051
 ] 

Chris Bowditch commented on FOP-2930:
-

I also don't approve of the proposed solution. I'd guess there is some image 
processing needed to convert images to format required by PDF and thats why it 
takes a long time to generate the PDF File. I think we should confirm before 
closing this bug

> performance problem in pdf generation
> -
>
> Key: FOP-2930
> URL: https://issues.apache.org/jira/browse/FOP-2930
> Project: FOP
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: zouari
>Priority: Major
> Fix For: 2.4
>
> Attachments: PDFFactory.patch, test1.if, test1.pdf
>
>
> I have an ".if" file which contains external document.
> this file contains 50,000 pages.
> I tried to convert it to pdf but this task took a long time
> we analyze this performance problem, I find for each external page, an object 
> "PDFResources".
> PDFResources objects processing slows down pdf file generation.
> solution:
> create a global "PDFResources" object for all the pages.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2894) Fit table contents onto current page

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner updated FOP-2894:
---
Fix Version/s: trunk

> Fit table contents onto current page
> 
>
> Key: FOP-2894
> URL: https://issues.apache.org/jira/browse/FOP-2894
> Project: FOP
>  Issue Type: Bug
>Reporter: Simon Steiner
>Assignee: Simon Steiner
>Priority: Major
> Fix For: trunk
>
> Attachments: test.fo
>
>
> fop test.fo out.pdf
> content should fit on one page



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2901) NoSuchElementException on empty table footer

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner updated FOP-2901:
---
Fix Version/s: trunk

> NoSuchElementException on empty table footer
> 
>
> Key: FOP-2901
> URL: https://issues.apache.org/jira/browse/FOP-2901
> Project: FOP
>  Issue Type: Bug
>Reporter: Simon Steiner
>Assignee: Simon Steiner
>Priority: Major
> Fix For: trunk
>
> Attachments: simple.fo
>
>
> fop simple.fo out.pdf -r
> java.util.NoSuchElementException
>  at java.util.LinkedList$ListItr.previous(LinkedList.java:905)
>  at 
> org.apache.fop.layoutmgr.table.TableContentLayoutManager.getKnuthElementsForRowIterator(TableContentLayoutManager.java:332)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2902) Ignore TTF reserved index range

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner updated FOP-2902:
---
Fix Version/s: trunk

> Ignore TTF reserved index range
> ---
>
> Key: FOP-2902
> URL: https://issues.apache.org/jira/browse/FOP-2902
> 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
>  
> Caused by: java.io.EOFException: Reached EOF, file size=50583
>  at 
> org.apache.fop.fonts.truetype.FontFileReader.readTTFString(FontFileReader.java:264)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2898) Only use zero glue for change ipd

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner updated FOP-2898:
---
Fix Version/s: trunk

> Only use zero glue for change ipd
> -
>
> Key: FOP-2898
> URL: https://issues.apache.org/jira/browse/FOP-2898
> Project: FOP
>  Issue Type: Bug
>Reporter: Simon Steiner
>Assignee: Simon Steiner
>Priority: Major
> Fix For: trunk
>
> Attachments: simple2.fo
>
>
> fop simple2.fo out.pdf
>  
> The table border should be close to the text



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2904) Handle object for boundingbox in mergefonts

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner updated FOP-2904:
---
Fix Version/s: trunk

> Handle object for boundingbox in mergefonts
> ---
>
> Key: FOP-2904
> URL: https://issues.apache.org/jira/browse/FOP-2904
> Project: FOP
>  Issue Type: Bug
>Reporter: Simon Steiner
>Assignee: Simon Steiner
>Priority: Major
> Fix For: trunk
>
> Attachments: fop.xconf, simple.pdf, test.fo
>
>
> fop test.fo -c fop.xconf out.pdf
>  
> java.lang.RuntimeException: Error on PDF page: simple.pdf 
> org.apache.pdfbox.cos.COSObject cannot be cast to 
> org.apache.pdfbox.cos.COSArray



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2907) Missing bounding box on repeated image for PDF/UA

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner updated FOP-2907:
---
Fix Version/s: trunk

> Missing bounding box on repeated image for PDF/UA
> -
>
> Key: FOP-2907
> URL: https://issues.apache.org/jira/browse/FOP-2907
> Project: FOP
>  Issue Type: Bug
>Reporter: Simon Steiner
>Assignee: Simon Steiner
>Priority: Major
> Fix For: trunk
>
> Attachments: fop.xconf, test.fo
>
>
> fop test.fo out.pdf -c fop.xconf
> Open with PAC3, no error should occur
>  [https://www.access-for-all.ch/en/pdf-lab/pdf-accessibility-checker-pac.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2895) Maven transcoder jar misses content

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner updated FOP-2895:
---
Fix Version/s: trunk

> Maven transcoder jar misses content
> ---
>
> Key: FOP-2895
> URL: https://issues.apache.org/jira/browse/FOP-2895
> Project: FOP
>  Issue Type: Bug
>  Components: unqualified
>Affects Versions: 2.4
>Reporter: Dimitry Polivaev
>Assignee: Simon Steiner
>Priority: Major
> Fix For: trunk
>
>
> Batik 1.12 uses PDFTranscoder from FOP 2.4 contained in jar file 
> fop-transcoder-allinone-2.4.jar included in binary distribution available as 
> batik/binaries/batik-bin-1.12.zip
> However packages org.apache.fop.configuration and org.apache.fop.config 
> contained in this file are missed in  fop-transcoder-allinone-2.4.jar  
> available as maven artifact  
> org.apache.xmlgraphics:fop-transcoder-allinone:2.4. It makes impossible to 
> use the maven artifact as expected.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2908) Repeated image in header not shown in structure tree

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner updated FOP-2908:
---
Fix Version/s: trunk

> Repeated image in header not shown in structure tree
> 
>
> Key: FOP-2908
> URL: https://issues.apache.org/jira/browse/FOP-2908
> Project: FOP
>  Issue Type: Bug
>Reporter: Simon Steiner
>Assignee: Simon Steiner
>Priority: Major
> Fix For: trunk
>
> Attachments: fop.xconf, test.fo
>
>
> fop test.fo out.pdf -c fop.xconf
> Open with PAC3, click logical structure, there should be 2 images under first 
> Figure tag
>  [https://www.access-for-all.ch/en/pdf-lab/pdf-accessibility-checker-pac.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2889) Missing maven artifacts: jai-core and jai-codec

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner updated FOP-2889:
---
Fix Version/s: trunk

> Missing maven artifacts: jai-core and jai-codec
> ---
>
> Key: FOP-2889
> URL: https://issues.apache.org/jira/browse/FOP-2889
> Project: FOP
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Jörg Weske
>Assignee: Simon Steiner
>Priority: Major
> Fix For: trunk
>
>
> +*Problem:*+ When trying to include FOP 2.4 in a Java Maven project, the 
> following artifacts cannot be found through maven-central:
> {noformat}
> 
>   javax.media
>   jai-core
>   1.1.3
> 
> 
>   com.sun.media
>   jai-codec
>   1.1.3
> {noformat}
> As a result, building the project is impossible.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2909) Hide empty blocks from structure tree

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner updated FOP-2909:
---
Fix Version/s: trunk

> Hide empty blocks from structure tree
> -
>
> Key: FOP-2909
> URL: https://issues.apache.org/jira/browse/FOP-2909
> Project: FOP
>  Issue Type: Bug
>Reporter: Simon Steiner
>Assignee: Simon Steiner
>Priority: Major
> Fix For: trunk
>
> Attachments: fop.xconf, simple.fo
>
>
> fop simple.fo out.pdf -c fop.xconf
> Open with PAC3, click screen reader preview, there shouldnt be empty P squares
>  [https://www.access-for-all.ch/en/pdf-lab/pdf-accessibility-checker-pac.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2925) Change in IPD on empty block NPE

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner updated FOP-2925:
---
Fix Version/s: trunk

> Change in IPD on empty block NPE
> 
>
> Key: FOP-2925
> URL: https://issues.apache.org/jira/browse/FOP-2925
> 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 exception should occur
> java.lang.NullPointerException
>  at 
> org.apache.fop.layoutmgr.AbstractBreaker.getRestartAtLM(AbstractBreaker.java:529)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2733) [PATCH] Drop dependency on Avalon-Framework

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner updated FOP-2733:
---
Fix Version/s: 2.4

> [PATCH] Drop dependency on Avalon-Framework
> ---
>
> Key: FOP-2733
> URL: https://issues.apache.org/jira/browse/FOP-2733
> Project: FOP
>  Issue Type: Bug
>Reporter: Chris West
>Assignee: Simon Steiner
>Priority: Major
> Fix For: 2.4
>
> Attachments: barcode.pdf, fop-no-avalon-1.patch
>
>
> FOP depends on avalon-framework, an old Apache project officially abandoned 
> in 2004. Nearly nobody uses avalon-framework anymore, and I'd like to see it 
> laid to rest.
> avalon-framework no-longer compiles with Java 9. Fixing it yet again seems 
> like insanity. This isn't a problem for Maven users, who can keep using the 
> old binary (and suffer slow verification on startup), but is a problem for 
> distros like Debian, who want to be able to build everything.
> Others have asked about this before, e.g. 
> http://apache-fop.1065347.n5.nabble.com/FOP-and-Avalon-td44302.html
> I propose removing the dependency on Avalon entirely, fixing the couple of 
> cases where it breaks, and inlining the two packages that are actually still 
> used.. I have created a patch here: 
> https://github.com/apache/fop/compare/trunk...FauxFaux:trunk , also attached.
> It's not great to read in patch form, so here's a summary of the changes:
>  * Remove dependence on avalon-framework from Maven, classpath variables etc.
>  * Add Avalon's configuration package as main:org.apache.fop.configuration 
> directly, and keep using it essentially unmodified.
>  * Add Avalon's logging framework as test:org.apache.fop.threading.logger. 
> This is only used in test code, in the threaded test code runner. It is 
> essentially source compatible with log4j/commons-logging, so could probably 
> be deleted.
>  * Change `CIDFontType` from a Avalon enum to a Java5 `enum`. This appears to 
> be source, but not binary, compatible.
>  * Remove some use of lifecycle management interfaces in test code, which are 
> not doing anything.
>  * Change some exception printing in test code to print the full exception 
> (using the Java api), instead of a truncated exception. The output is not 
> asserted upon, just sent to stderr.
>  * Stop using Cascading*Exception in tests, and for ConfigurationException. I 
> doubt anyone will notice, as it offers no real functionality.
> That's it!
> The most controversial thing here is probably adding the configuration 
> package, and the extra lines of code it drags along with it. I am happy to 
> give it a bit of a polish; make significant changes to fop to remove all the 
> unused interfaces / abstract classes (which are just waste); put some 
> generics and formatting in, etc.?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2924) Images not scaled or rotated in PCL

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner updated FOP-2924:
---
Fix Version/s: trunk

> Images not scaled or rotated in PCL
> ---
>
> Key: FOP-2924
> URL: https://issues.apache.org/jira/browse/FOP-2924
> Project: FOP
>  Issue Type: Bug
>Reporter: Simon Steiner
>Assignee: Simon Steiner
>Priority: Major
> Fix For: trunk
>
> Attachments: test.fo
>
>
> fop test.fo -pcl out.pcl
> Barcode should be horizontal



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2926) Add artifact type to PDF header/footer

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner updated FOP-2926:
---
Fix Version/s: trunk

> Add artifact type to PDF header/footer
> --
>
> Key: FOP-2926
> URL: https://issues.apache.org/jira/browse/FOP-2926
> Project: FOP
>  Issue Type: Bug
>Reporter: Simon Steiner
>Assignee: Simon Steiner
>Priority: Major
> Fix For: trunk
>
> Attachments: fop.xconf, test4.fo
>
>
> fop test4.fo -c fop.xconf out.pdf
> Open PDF with PAC3, click Logical structure, artifacts, each footer element 
> should have a type and a subtype
>  [https://www.access-for-all.ch/en/pdf-lab/pdf-accessibility-checker-pac.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2233) RSS-feed link on website broken

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner updated FOP-2233:
---
Fix Version/s: trunk

> RSS-feed link on website broken
> ---
>
> Key: FOP-2233
> URL: https://issues.apache.org/jira/browse/FOP-2233
> Project: FOP
>  Issue Type: Bug
>  Components: documentation
> Environment:  
>Reporter: paull lachewsky
>Assignee: Simon Steiner
>Priority: Minor
> Fix For: trunk
>
>
> The RSS-link for the FOP news ist broken
> Page:http://xmlgraphics.apache.org/fop/news.html
> Link: http://xmlgraphics.apache.org/fop/subproject-news-feed.rss
> Couldn't find any contact-information regarding webmaster/mistress, so I 
> figured I'd need to file a bug.. Hope that's okay
> imho rss-feeds are the best thing to stay updated with software-news. I'd be 
> very happy if you can fix it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2911) Add endpage event for FO to IF

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner updated FOP-2911:
---
Fix Version/s: trunk

> Add endpage event for FO to IF
> --
>
> Key: FOP-2911
> URL: https://issues.apache.org/jira/browse/FOP-2911
> Project: FOP
>  Issue Type: Bug
>Reporter: Simon Steiner
>Assignee: Simon Steiner
>Priority: Major
> Fix For: trunk
>
>
> To catch a infinite loop inside FO to IF you can monitor the end page events, 
> events later in the pipeline would be too late



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2923) Allow to suppress fo:leader within empty paragaphs from structure tree

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner updated FOP-2923:
---
Fix Version/s: trunk

> Allow to suppress fo:leader within empty paragaphs from structure tree
> --
>
> Key: FOP-2923
> URL: https://issues.apache.org/jira/browse/FOP-2923
> Project: FOP
>  Issue Type: Bug
>Reporter: Simon Steiner
>Assignee: Simon Steiner
>Priority: Major
> Fix For: trunk
>
> Attachments: fop.xconf, test3.fo
>
>
> fop test3.fo -c fop.xconf out.pdf
>  
> open with PAC3, no empty P should be shown in Screen Reader preview
>  [https://www.access-for-all.ch/en/pdf-lab/pdf-accessibility-checker-pac.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2922) PDF to PDF syntax error after writing content stream

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner updated FOP-2922:
---
Fix Version/s: trunk

> PDF to PDF syntax error after writing content stream
> 
>
> Key: FOP-2922
> URL: https://issues.apache.org/jira/browse/FOP-2922
> Project: FOP
>  Issue Type: Bug
>Reporter: Simon Steiner
>Assignee: Simon Steiner
>Priority: Major
> Fix For: trunk
>
> Attachments: in.pdf, test.fo
>
>
> fop test.fo out.pdf
> There should be a space between each boolean values in content stream



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FOP-2704) [PATCH] Google fonts Roboto font (updated 2017) UnsupportedOperationException: coverage set class table not yet supported

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner updated FOP-2704:
---
Fix Version/s: trunk

> [PATCH] Google fonts Roboto font (updated 2017) 
> UnsupportedOperationException: coverage set class table not yet supported
> -
>
> Key: FOP-2704
> URL: https://issues.apache.org/jira/browse/FOP-2704
> Project: FOP
>  Issue Type: Bug
>  Components: font/opentype
>Affects Versions: 2.1, 2.2
>Reporter: Dan Caprioara
>Assignee: Simon Steiner
>Priority: Major
> Fix For: trunk
>
> Attachments: Roboto-Regular.ttf, Roboto-Thin.ttf, 
> font-workaround.patch
>
>
> Steps:
> # Download the Roboto TTF font from Google Fonts. 
> # Create a configuration file with a triplet pointing to the "roboto-regular" 
> or "roboto-thin" TTF file.
> You get:
> {code}
> java.lang.UnsupportedOperationException: coverage set class table not yet 
> supported
>   at 
> org.apache.fop.complexscripts.fonts.GlyphClassTable$CoverageSetClassTable.(GlyphClassTable.java:262)
>   at 
> org.apache.fop.complexscripts.fonts.GlyphClassTable.createClassTable(GlyphClassTable.java:88)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readGDEFMarkGlyphsTableFormat1(OTFAdvancedTypographicTableReader_Original.java:3344)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader.readGDEFMarkGlyphsTableFormat1(OTFAdvancedTypographicTableReader.java:69)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readGDEFMarkGlyphsTable(OTFAdvancedTypographicTableReader_Original.java:3357)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readGDEF(OTFAdvancedTypographicTableReader_Original.java:3427)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readAll(OTFAdvancedTypographicTableReader_Original.java:80)
>   at 
> org.apache.fop.fonts.truetype.OpenFont.handleCharacterSpacing(OpenFont.java:786)
>   at org.apache.fop.fonts.truetype.OpenFont.readFont(OpenFont.java:755)
>   at 
> org.apache.fop.fonts.truetype.OFFontLoader.read(OFFontLoader.java:109)
>   at org.apache.fop.fonts.truetype.OFFontLoader.read(OFFontLoader.java:93)
> {code}
> There are two changes that should be done to the 
> {{OTFAdvancedTypographicTableReader}}.
> # The method {{readGDEFMarkGlyphsTableFormat1}} should catch this exception
> # The method {{constructLookupsLanguage}} should check if the {{languages}} 
> parameter is null.
> After these changes, the PDF is produced and it looks good. I am not sure 
> what are the side effects on the font that is embedded into the PDF..



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Comment Edited] (FOP-2704) [PATCH] Google fonts Roboto font (updated 2017) UnsupportedOperationException: coverage set class table not yet supported

2020-04-15 Thread Simon Steiner (Jira)


[ 
https://issues.apache.org/jira/browse/FOP-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083941#comment-17083941
 ] 

Simon Steiner edited comment on FOP-2704 at 4/15/20, 9:13 AM:
--

The release notification goes to the fop mailing lists


was (Author: ssteiner1):
The release notification goes to the fop mailing lists, I added but not sure if 
you can watch this:

https://issues.apache.org/jira/projects/FOP/versions/12348082

> [PATCH] Google fonts Roboto font (updated 2017) 
> UnsupportedOperationException: coverage set class table not yet supported
> -
>
> Key: FOP-2704
> URL: https://issues.apache.org/jira/browse/FOP-2704
> Project: FOP
>  Issue Type: Bug
>  Components: font/opentype
>Affects Versions: 2.1, 2.2
>Reporter: Dan Caprioara
>Assignee: Simon Steiner
>Priority: Major
> Attachments: Roboto-Regular.ttf, Roboto-Thin.ttf, 
> font-workaround.patch
>
>
> Steps:
> # Download the Roboto TTF font from Google Fonts. 
> # Create a configuration file with a triplet pointing to the "roboto-regular" 
> or "roboto-thin" TTF file.
> You get:
> {code}
> java.lang.UnsupportedOperationException: coverage set class table not yet 
> supported
>   at 
> org.apache.fop.complexscripts.fonts.GlyphClassTable$CoverageSetClassTable.(GlyphClassTable.java:262)
>   at 
> org.apache.fop.complexscripts.fonts.GlyphClassTable.createClassTable(GlyphClassTable.java:88)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readGDEFMarkGlyphsTableFormat1(OTFAdvancedTypographicTableReader_Original.java:3344)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader.readGDEFMarkGlyphsTableFormat1(OTFAdvancedTypographicTableReader.java:69)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readGDEFMarkGlyphsTable(OTFAdvancedTypographicTableReader_Original.java:3357)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readGDEF(OTFAdvancedTypographicTableReader_Original.java:3427)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readAll(OTFAdvancedTypographicTableReader_Original.java:80)
>   at 
> org.apache.fop.fonts.truetype.OpenFont.handleCharacterSpacing(OpenFont.java:786)
>   at org.apache.fop.fonts.truetype.OpenFont.readFont(OpenFont.java:755)
>   at 
> org.apache.fop.fonts.truetype.OFFontLoader.read(OFFontLoader.java:109)
>   at org.apache.fop.fonts.truetype.OFFontLoader.read(OFFontLoader.java:93)
> {code}
> There are two changes that should be done to the 
> {{OTFAdvancedTypographicTableReader}}.
> # The method {{readGDEFMarkGlyphsTableFormat1}} should catch this exception
> # The method {{constructLookupsLanguage}} should check if the {{languages}} 
> parameter is null.
> After these changes, the PDF is produced and it looks good. I am not sure 
> what are the side effects on the font that is embedded into the PDF..



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (FOP-2704) [PATCH] Google fonts Roboto font (updated 2017) UnsupportedOperationException: coverage set class table not yet supported

2020-04-15 Thread Simon Steiner (Jira)


[ 
https://issues.apache.org/jira/browse/FOP-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083941#comment-17083941
 ] 

Simon Steiner commented on FOP-2704:


The release notification goes to the fop mailing lists, I added but not sure if 
you can watch this:

https://issues.apache.org/jira/projects/FOP/versions/12348082

> [PATCH] Google fonts Roboto font (updated 2017) 
> UnsupportedOperationException: coverage set class table not yet supported
> -
>
> Key: FOP-2704
> URL: https://issues.apache.org/jira/browse/FOP-2704
> Project: FOP
>  Issue Type: Bug
>  Components: font/opentype
>Affects Versions: 2.1, 2.2
>Reporter: Dan Caprioara
>Assignee: Simon Steiner
>Priority: Major
> Attachments: Roboto-Regular.ttf, Roboto-Thin.ttf, 
> font-workaround.patch
>
>
> Steps:
> # Download the Roboto TTF font from Google Fonts. 
> # Create a configuration file with a triplet pointing to the "roboto-regular" 
> or "roboto-thin" TTF file.
> You get:
> {code}
> java.lang.UnsupportedOperationException: coverage set class table not yet 
> supported
>   at 
> org.apache.fop.complexscripts.fonts.GlyphClassTable$CoverageSetClassTable.(GlyphClassTable.java:262)
>   at 
> org.apache.fop.complexscripts.fonts.GlyphClassTable.createClassTable(GlyphClassTable.java:88)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readGDEFMarkGlyphsTableFormat1(OTFAdvancedTypographicTableReader_Original.java:3344)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader.readGDEFMarkGlyphsTableFormat1(OTFAdvancedTypographicTableReader.java:69)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readGDEFMarkGlyphsTable(OTFAdvancedTypographicTableReader_Original.java:3357)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readGDEF(OTFAdvancedTypographicTableReader_Original.java:3427)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readAll(OTFAdvancedTypographicTableReader_Original.java:80)
>   at 
> org.apache.fop.fonts.truetype.OpenFont.handleCharacterSpacing(OpenFont.java:786)
>   at org.apache.fop.fonts.truetype.OpenFont.readFont(OpenFont.java:755)
>   at 
> org.apache.fop.fonts.truetype.OFFontLoader.read(OFFontLoader.java:109)
>   at org.apache.fop.fonts.truetype.OFFontLoader.read(OFFontLoader.java:93)
> {code}
> There are two changes that should be done to the 
> {{OTFAdvancedTypographicTableReader}}.
> # The method {{readGDEFMarkGlyphsTableFormat1}} should catch this exception
> # The method {{constructLookupsLanguage}} should check if the {{languages}} 
> parameter is null.
> After these changes, the PDF is produced and it looks good. I am not sure 
> what are the side effects on the font that is embedded into the PDF..



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: Xmp properties non-compact values representation only for PDF/A

2020-04-15 Thread Chris Bowditch

Hi,

Isn't  a compact representation preferable as it helps keep the file 
size down?


Thanks,

Chris

On 26/03/2020 17:32, franck FIMBEL wrote:

Hi
Currently its seems that FOP output XMP properties like dc:language in
a non compact representation (including Bag and li elements) only when
rendering pdf/a but it outputs a compact representation in standard
pdf rendering.
dc.setCompact(pdfaMode.getPart() != 3); in PdfMetadata class line 149

Is there any specific reason to keep the compact representation for
PDF ? If so, could it be a pdf rendering parameter ?

Thanks





[jira] [Commented] (FOP-2704) [PATCH] Google fonts Roboto font (updated 2017) UnsupportedOperationException: coverage set class table not yet supported

2020-04-15 Thread Matthias Pigulla (Jira)


[ 
https://issues.apache.org/jira/browse/FOP-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083925#comment-17083925
 ] 

Matthias Pigulla commented on FOP-2704:
---

[~ssteiner] Thank you for working on this!

As a JIRA user, will I get another notification once this makes it into a 
release, or should I watch releases separately?


> [PATCH] Google fonts Roboto font (updated 2017) 
> UnsupportedOperationException: coverage set class table not yet supported
> -
>
> Key: FOP-2704
> URL: https://issues.apache.org/jira/browse/FOP-2704
> Project: FOP
>  Issue Type: Bug
>  Components: font/opentype
>Affects Versions: 2.1, 2.2
>Reporter: Dan Caprioara
>Assignee: Simon Steiner
>Priority: Major
> Attachments: Roboto-Regular.ttf, Roboto-Thin.ttf, 
> font-workaround.patch
>
>
> Steps:
> # Download the Roboto TTF font from Google Fonts. 
> # Create a configuration file with a triplet pointing to the "roboto-regular" 
> or "roboto-thin" TTF file.
> You get:
> {code}
> java.lang.UnsupportedOperationException: coverage set class table not yet 
> supported
>   at 
> org.apache.fop.complexscripts.fonts.GlyphClassTable$CoverageSetClassTable.(GlyphClassTable.java:262)
>   at 
> org.apache.fop.complexscripts.fonts.GlyphClassTable.createClassTable(GlyphClassTable.java:88)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readGDEFMarkGlyphsTableFormat1(OTFAdvancedTypographicTableReader_Original.java:3344)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader.readGDEFMarkGlyphsTableFormat1(OTFAdvancedTypographicTableReader.java:69)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readGDEFMarkGlyphsTable(OTFAdvancedTypographicTableReader_Original.java:3357)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readGDEF(OTFAdvancedTypographicTableReader_Original.java:3427)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readAll(OTFAdvancedTypographicTableReader_Original.java:80)
>   at 
> org.apache.fop.fonts.truetype.OpenFont.handleCharacterSpacing(OpenFont.java:786)
>   at org.apache.fop.fonts.truetype.OpenFont.readFont(OpenFont.java:755)
>   at 
> org.apache.fop.fonts.truetype.OFFontLoader.read(OFFontLoader.java:109)
>   at org.apache.fop.fonts.truetype.OFFontLoader.read(OFFontLoader.java:93)
> {code}
> There are two changes that should be done to the 
> {{OTFAdvancedTypographicTableReader}}.
> # The method {{readGDEFMarkGlyphsTableFormat1}} should catch this exception
> # The method {{constructLookupsLanguage}} should check if the {{languages}} 
> parameter is null.
> After these changes, the PDF is produced and it looks good. I am not sure 
> what are the side effects on the font that is embedded into the PDF..



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (FOP-2704) [PATCH] Google fonts Roboto font (updated 2017) UnsupportedOperationException: coverage set class table not yet supported

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner resolved FOP-2704.

Resolution: Fixed

http://svn.apache.org/viewvc?view=revision&revision=1876539

> [PATCH] Google fonts Roboto font (updated 2017) 
> UnsupportedOperationException: coverage set class table not yet supported
> -
>
> Key: FOP-2704
> URL: https://issues.apache.org/jira/browse/FOP-2704
> Project: FOP
>  Issue Type: Bug
>  Components: font/opentype
>Affects Versions: 2.1, 2.2
>Reporter: Dan Caprioara
>Assignee: Simon Steiner
>Priority: Major
> Attachments: Roboto-Regular.ttf, Roboto-Thin.ttf, 
> font-workaround.patch
>
>
> Steps:
> # Download the Roboto TTF font from Google Fonts. 
> # Create a configuration file with a triplet pointing to the "roboto-regular" 
> or "roboto-thin" TTF file.
> You get:
> {code}
> java.lang.UnsupportedOperationException: coverage set class table not yet 
> supported
>   at 
> org.apache.fop.complexscripts.fonts.GlyphClassTable$CoverageSetClassTable.(GlyphClassTable.java:262)
>   at 
> org.apache.fop.complexscripts.fonts.GlyphClassTable.createClassTable(GlyphClassTable.java:88)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readGDEFMarkGlyphsTableFormat1(OTFAdvancedTypographicTableReader_Original.java:3344)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader.readGDEFMarkGlyphsTableFormat1(OTFAdvancedTypographicTableReader.java:69)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readGDEFMarkGlyphsTable(OTFAdvancedTypographicTableReader_Original.java:3357)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readGDEF(OTFAdvancedTypographicTableReader_Original.java:3427)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readAll(OTFAdvancedTypographicTableReader_Original.java:80)
>   at 
> org.apache.fop.fonts.truetype.OpenFont.handleCharacterSpacing(OpenFont.java:786)
>   at org.apache.fop.fonts.truetype.OpenFont.readFont(OpenFont.java:755)
>   at 
> org.apache.fop.fonts.truetype.OFFontLoader.read(OFFontLoader.java:109)
>   at org.apache.fop.fonts.truetype.OFFontLoader.read(OFFontLoader.java:93)
> {code}
> There are two changes that should be done to the 
> {{OTFAdvancedTypographicTableReader}}.
> # The method {{readGDEFMarkGlyphsTableFormat1}} should catch this exception
> # The method {{constructLookupsLanguage}} should check if the {{languages}} 
> parameter is null.
> After these changes, the PDF is produced and it looks good. I am not sure 
> what are the side effects on the font that is embedded into the PDF..



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (FOP-2704) [PATCH] Google fonts Roboto font (updated 2017) UnsupportedOperationException: coverage set class table not yet supported

2020-04-15 Thread Simon Steiner (Jira)


 [ 
https://issues.apache.org/jira/browse/FOP-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Steiner reassigned FOP-2704:
--

Assignee: Simon Steiner

> [PATCH] Google fonts Roboto font (updated 2017) 
> UnsupportedOperationException: coverage set class table not yet supported
> -
>
> Key: FOP-2704
> URL: https://issues.apache.org/jira/browse/FOP-2704
> Project: FOP
>  Issue Type: Bug
>  Components: font/opentype
>Affects Versions: 2.1, 2.2
>Reporter: Dan Caprioara
>Assignee: Simon Steiner
>Priority: Major
> Attachments: Roboto-Regular.ttf, Roboto-Thin.ttf, 
> font-workaround.patch
>
>
> Steps:
> # Download the Roboto TTF font from Google Fonts. 
> # Create a configuration file with a triplet pointing to the "roboto-regular" 
> or "roboto-thin" TTF file.
> You get:
> {code}
> java.lang.UnsupportedOperationException: coverage set class table not yet 
> supported
>   at 
> org.apache.fop.complexscripts.fonts.GlyphClassTable$CoverageSetClassTable.(GlyphClassTable.java:262)
>   at 
> org.apache.fop.complexscripts.fonts.GlyphClassTable.createClassTable(GlyphClassTable.java:88)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readGDEFMarkGlyphsTableFormat1(OTFAdvancedTypographicTableReader_Original.java:3344)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader.readGDEFMarkGlyphsTableFormat1(OTFAdvancedTypographicTableReader.java:69)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readGDEFMarkGlyphsTable(OTFAdvancedTypographicTableReader_Original.java:3357)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readGDEF(OTFAdvancedTypographicTableReader_Original.java:3427)
>   at 
> org.apache.fop.complexscripts.fonts.OTFAdvancedTypographicTableReader_Original.readAll(OTFAdvancedTypographicTableReader_Original.java:80)
>   at 
> org.apache.fop.fonts.truetype.OpenFont.handleCharacterSpacing(OpenFont.java:786)
>   at org.apache.fop.fonts.truetype.OpenFont.readFont(OpenFont.java:755)
>   at 
> org.apache.fop.fonts.truetype.OFFontLoader.read(OFFontLoader.java:109)
>   at org.apache.fop.fonts.truetype.OFFontLoader.read(OFFontLoader.java:93)
> {code}
> There are two changes that should be done to the 
> {{OTFAdvancedTypographicTableReader}}.
> # The method {{readGDEFMarkGlyphsTableFormat1}} should catch this exception
> # The method {{constructLookupsLanguage}} should check if the {{languages}} 
> parameter is null.
> After these changes, the PDF is produced and it looks good. I am not sure 
> what are the side effects on the font that is embedded into the PDF..



--
This message was sent by Atlassian Jira
(v8.3.4#803005)