[jira] [Closed] (FOP-2849) Scaling of Grayscale Windows BMP
[ https://issues.apache.org/jira/browse/FOP-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Hegny closed FOP-2849. - Resolution: Invalid Should go to xmlgraphics with more details > Scaling of Grayscale Windows BMP > > > Key: FOP-2849 > URL: https://issues.apache.org/jira/browse/FOP-2849 > Project: FOP > Issue Type: Bug > Components: image/unqualified >Affects Versions: 2.2 > Environment: Linux >Reporter: Stefan Hegny >Priority: Minor > Attachments: big.bmp, big.fo > > > I'm using external-graphics with grayscale 8bit Windows BMP Files. Whenever > the Image has to be scaled down, in the pdf it is flipped horizontally, > acutally not keeping its aspect ratio, and the grayscales look dim. See > big.fo. Sometimes when using imagemagic convert (-depth 8 -colors 256 -type > grayscale) I also managed to get it flipped vertically and goes out of the > block at the top. > Extracting the image with pdfimages gives a ppm, its aspect rafio is correct > but still the colours are dim. > FO Files and sample BMPs are attached and here: > [https://www.magentacloud.de/share/6x.svy3pz9] > The small works ok, the big shows the described effect with FOP 2.2 - Im not > sure if the issue is FOP of the Java Image IO, please advise > Thanks & regards, Stefan -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FOP-2849) Scaling of Grayscale Windows BMP
[ https://issues.apache.org/jira/browse/FOP-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794461#comment-16794461 ] Stefan Hegny commented on FOP-2849: --- I'm closing this and repoen at xmlgraphics. Sorry guis. > Scaling of Grayscale Windows BMP > > > Key: FOP-2849 > URL: https://issues.apache.org/jira/browse/FOP-2849 > Project: FOP > Issue Type: Bug > Components: image/unqualified >Affects Versions: 2.2 > Environment: Linux >Reporter: Stefan Hegny >Priority: Minor > Attachments: big.bmp, big.fo > > > I'm using external-graphics with grayscale 8bit Windows BMP Files. Whenever > the Image has to be scaled down, in the pdf it is flipped horizontally, > acutally not keeping its aspect ratio, and the grayscales look dim. See > big.fo. Sometimes when using imagemagic convert (-depth 8 -colors 256 -type > grayscale) I also managed to get it flipped vertically and goes out of the > block at the top. > Extracting the image with pdfimages gives a ppm, its aspect rafio is correct > but still the colours are dim. > FO Files and sample BMPs are attached and here: > [https://www.magentacloud.de/share/6x.svy3pz9] > The small works ok, the big shows the described effect with FOP 2.2 - Im not > sure if the issue is FOP of the Java Image IO, please advise > Thanks & regards, Stefan -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FOP-2849) Scaling of Grayscale Windows BMP
[ https://issues.apache.org/jira/browse/FOP-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782870#comment-16782870 ] Stefan Hegny commented on FOP-2849: --- The issue seems to be the value "1" thats inside these BMPs at the horizontal / vertical resolution. Placing 0 at that value makes the images well-behaved. Probably not fop error at all, sorry! > Scaling of Grayscale Windows BMP > > > Key: FOP-2849 > URL: https://issues.apache.org/jira/browse/FOP-2849 > Project: FOP > Issue Type: Bug > Components: image/unqualified >Affects Versions: 2.2 > Environment: Linux >Reporter: Stefan Hegny >Priority: Minor > Attachments: big.bmp, big.fo > > > I'm using external-graphics with grayscale 8bit Windows BMP Files. Whenever > the Image has to be scaled down, in the pdf it is flipped horizontally, > acutally not keeping its aspect ratio, and the grayscales look dim. See > big.fo. Sometimes when using imagemagic convert (-depth 8 -colors 256 -type > grayscale) I also managed to get it flipped vertically and goes out of the > block at the top. > Extracting the image with pdfimages gives a ppm, its aspect rafio is correct > but still the colours are dim. > FO Files and sample BMPs are attached and here: > [https://www.magentacloud.de/share/6x.svy3pz9] > The small works ok, the big shows the described effect with FOP 2.2 - Im not > sure if the issue is FOP of the Java Image IO, please advise > Thanks & regards, Stefan -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FOP-2849) Scaling of Grayscale Windows BMP
Stefan Hegny created FOP-2849: - Summary: Scaling of Grayscale Windows BMP Key: FOP-2849 URL: https://issues.apache.org/jira/browse/FOP-2849 Project: FOP Issue Type: Bug Components: image/unqualified Affects Versions: 2.2 Environment: Linux Reporter: Stefan Hegny Attachments: big.bmp, big.fo I'm using external-graphics with grayscale 8bit Windows BMP Files. Whenever the Image has to be scaled down, in the pdf it is flipped horizontally, acutally not keeping its aspect ratio, and the grayscales look dim. See big.fo. Sometimes when using imagemagic convert (-depth 8 -colors 256 -type grayscale) I also managed to get it flipped vertically and goes out of the block at the top. Extracting the image with pdfimages gives a ppm, its aspect rafio is correct but still the colours are dim. FO Files and sample BMPs are attached and here: [https://www.magentacloud.de/share/6x.svy3pz9] The small works ok, the big shows the described effect with FOP 2.2 - Im not sure if the issue is FOP of the Java Image IO, please advise Thanks & regards, Stefan -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FOP-2621) ToUnicode missing for AdobeStandardEncoding Fonts but present for FontSpecific
[ https://issues.apache.org/jira/browse/FOP-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Hegny resolved FOP-2621. --- Resolution: Fixed Fix Version/s: 2.2 not reproducible using fop 2.2 even using the https://www.pdf-online.com/osa/validate.aspx online validator. > ToUnicode missing for AdobeStandardEncoding Fonts but present for FontSpecific > -- > > Key: FOP-2621 > URL: https://issues.apache.org/jira/browse/FOP-2621 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.1 > Environment: Linux > java version "1.8.0_73" > Java(TM) SE Runtime Environment (build 1.8.0_73-b02) > Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode) > java version "1.7.0_95" > OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1) > OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode) >Reporter: Stefan Hegny >Priority: Minor > Labels: encoding, pdf/a > Fix For: 2.2 > > Attachments: buggele1.tar.gz > > > Generating PDF/A-1a gives non-validating pdf due to missing ToUnicode tables > for embedded AdobeStandardEncoding Fonts (e.g. Nimbus Roman 9L from > ghostscript, but also commercial T1 fonts). Validation here refers to the > online validator at pdf-tools.com . > Fonts embedded with FontSpecific Encoding produce ToUnicode tables. > Using modified .afm files where AdobeStandardEncoding is manually replaced by > FontSpecific will produce the ToUnicode tables for these fonts too and then > the resulting PDF will validate. The Files look identical to those > non-validating due to AdobeStandardEncoding also for more complex documents. > fop-2.1/fop -c working.xconf -a -pdfprofile 'PDF/A-1a' -pdf test_works.pdf > -fo test_0.fo > fop-2.1/fop -c notworking.xconf -a -pdfprofile 'PDF/A-1a' -pdf > test_notvalid.pdf -fo test_0.fo -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FOP-2621) ToUnicode missing for AdobeStandardEncoding Fonts but present for FontSpecific
[ https://issues.apache.org/jira/browse/FOP-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972360#comment-15972360 ] Stefan Hegny commented on FOP-2621: --- Seems the issue can *not* be reproduced using the verapdf validator even with fop 2.1 nor with fop 2.2. > ToUnicode missing for AdobeStandardEncoding Fonts but present for FontSpecific > -- > > Key: FOP-2621 > URL: https://issues.apache.org/jira/browse/FOP-2621 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.1 > Environment: Linux > java version "1.8.0_73" > Java(TM) SE Runtime Environment (build 1.8.0_73-b02) > Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode) > java version "1.7.0_95" > OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1) > OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode) >Reporter: Stefan Hegny >Priority: Minor > Labels: encoding, pdf/a > Attachments: buggele1.tar.gz > > > Generating PDF/A-1a gives non-validating pdf due to missing ToUnicode tables > for embedded AdobeStandardEncoding Fonts (e.g. Nimbus Roman 9L from > ghostscript, but also commercial T1 fonts). Validation here refers to the > online validator at pdf-tools.com . > Fonts embedded with FontSpecific Encoding produce ToUnicode tables. > Using modified .afm files where AdobeStandardEncoding is manually replaced by > FontSpecific will produce the ToUnicode tables for these fonts too and then > the resulting PDF will validate. The Files look identical to those > non-validating due to AdobeStandardEncoding also for more complex documents. > fop-2.1/fop -c working.xconf -a -pdfprofile 'PDF/A-1a' -pdf test_works.pdf > -fo test_0.fo > fop-2.1/fop -c notworking.xconf -a -pdfprofile 'PDF/A-1a' -pdf > test_notvalid.pdf -fo test_0.fo -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (FOP-2639) CIDSet error when PDF/A validating fop output with Linux Libertine OTF
[
https://issues.apache.org/jira/browse/FOP-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Hegny closed FOP-2639.
-
Resolution: Not A Bug
> CIDSet error when PDF/A validating fop output with Linux Libertine OTF
> --
>
> Key: FOP-2639
> URL: https://issues.apache.org/jira/browse/FOP-2639
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.1
> Environment: linux, java version "1.7.0_101"
> OpenJDK Runtime Environment (IcedTea 2.6.6) (7u101-2.6.6-2~deb7u1)
> OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
>Reporter: Stefan Hegny
>Priority: Minor
> Labels: pdf/a
> Attachments: testlibertine.fo, testlibertine.pdf
>
>
> Using the font LinLibertine_R.otf from the latest 5.3 release
> (http://sourceforge.net/projects/linuxlibertine/files/linuxlibertine/5.3.0/)
> in xsl-fo and requesting PDF/A-1a conformance gives validation error on
> https://www.pdf-tools.com/pdf/pdfa-online-pruefen.aspx:
> brief_DE_letter_PG_1_ovlsame.pdf does not conform to PDF/A.
> {noformat}
> Validating file "brief_DE_letter_PG_1_ovlsame.pdf" for conformance level
> pdfa-1a
> The value of the CIDSet[2] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[3] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[4] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[5] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[6] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[7] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[8] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[9] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[10] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[11] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[12] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[25] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[28] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[29] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[30] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[31] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[32] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[33] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[44] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[45] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[50] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[55] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[57] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[58] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[59] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[60] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[61] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[62] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[63] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[64] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The document does not conform to the requested standard.
> The document contains fonts without embedded font programs or encoding
> information (CMAPs).
> {noformat}
> Will attach sample fo input file, relevant config lines are
> {{ embed-url="file:///home/hegny/temp/libertine-5.3/LinLibertine_R.otf">}}
> {{}}
> {{}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FOP-2639) CIDSet error when PDF/A validating fop output with Linux Libertine OTF
[
https://issues.apache.org/jira/browse/FOP-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405506#comment-15405506
]
Stefan Hegny commented on FOP-2639:
---
Thanks @simonsteiner, I see... The core prob here is that I might have to add a
bold variant to commercial pfb's I've bought long ago and these today are
available only as otf fonts (though they might behave different from the
LinLibertine Fonts but I used these for trying). Adding the
embedding-mode="full" with pdf/a-1a and pdf version 1.4 will throw a nasty
exception "org.apache.fop.apps.FOPException: Cannot change the version of this
PDF document.". Using the libertine TTF fonts produces valid pdf/a-1a
(according to the mentioned pdf-tools.com validator)
So I see that what I describe is not a problem and probably I should close the
issue and try to get pfb or ttf variants of the commercial stuff I need -
thanks again
> CIDSet error when PDF/A validating fop output with Linux Libertine OTF
> --
>
> Key: FOP-2639
> URL: https://issues.apache.org/jira/browse/FOP-2639
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.1
> Environment: linux, java version "1.7.0_101"
> OpenJDK Runtime Environment (IcedTea 2.6.6) (7u101-2.6.6-2~deb7u1)
> OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
>Reporter: Stefan Hegny
>Priority: Minor
> Labels: pdf/a
> Attachments: testlibertine.fo, testlibertine.pdf
>
>
> Using the font LinLibertine_R.otf from the latest 5.3 release
> (http://sourceforge.net/projects/linuxlibertine/files/linuxlibertine/5.3.0/)
> in xsl-fo and requesting PDF/A-1a conformance gives validation error on
> https://www.pdf-tools.com/pdf/pdfa-online-pruefen.aspx:
> brief_DE_letter_PG_1_ovlsame.pdf does not conform to PDF/A.
> {noformat}
> Validating file "brief_DE_letter_PG_1_ovlsame.pdf" for conformance level
> pdfa-1a
> The value of the CIDSet[2] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[3] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[4] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[5] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[6] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[7] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[8] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[9] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[10] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[11] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[12] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[25] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[28] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[29] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[30] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[31] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[32] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[33] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[44] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[45] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[50] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[55] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[57] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[58] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[59] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[60] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[61] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[62] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[63] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the
[jira] [Commented] (FOP-2639) CIDSet error when PDF/A validating fop output with Linux Libertine OTF
[
https://issues.apache.org/jira/browse/FOP-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402199#comment-15402199
]
Stefan Hegny commented on FOP-2639:
---
Please dont get confused by the mention of EA+LinuxLibertineCapitalsO in
the validator output, should read EA+LinLibertineO for the _R sample
> CIDSet error when PDF/A validating fop output with Linux Libertine OTF
> --
>
> Key: FOP-2639
> URL: https://issues.apache.org/jira/browse/FOP-2639
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.1
> Environment: linux, java version "1.7.0_101"
> OpenJDK Runtime Environment (IcedTea 2.6.6) (7u101-2.6.6-2~deb7u1)
> OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
>Reporter: Stefan Hegny
>Priority: Minor
> Labels: pdf/a
> Attachments: testlibertine.fo, testlibertine.pdf
>
>
> Using the font LinLibertine_R.otf from the latest 5.3 release
> (http://sourceforge.net/projects/linuxlibertine/files/linuxlibertine/5.3.0/)
> in xsl-fo and requesting PDF/A-1a conformance gives validation error on
> https://www.pdf-tools.com/pdf/pdfa-online-pruefen.aspx:
> brief_DE_letter_PG_1_ovlsame.pdf does not conform to PDF/A.
> {noformat}
> Validating file "brief_DE_letter_PG_1_ovlsame.pdf" for conformance level
> pdfa-1a
> The value of the CIDSet[2] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[3] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[4] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[5] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[6] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[7] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[8] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[9] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[10] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[11] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[12] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[25] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[28] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[29] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[30] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[31] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[32] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[33] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[44] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[45] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[50] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[55] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[57] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[58] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[59] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[60] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[61] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[62] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[63] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[64] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The document does not conform to the requested standard.
> The document contains fonts without embedded font programs or encoding
> information (CMAPs).
> {noformat}
> Will attach sample fo input file, relevant config lines are
> {{ embed-url="file:///home/hegny/temp/libertine-5.3/LinLibertine_R.otf">}}
> {{}}
> {{}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FOP-2639) CIDSet error when PDF/A validating fop output with Linux Libertine OTF
[
https://issues.apache.org/jira/browse/FOP-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Hegny updated FOP-2639:
--
Attachment: testlibertine.pdf
fop 2.1 pdf output (pdf 1.4 as for pdf/a-1a)
> CIDSet error when PDF/A validating fop output with Linux Libertine OTF
> --
>
> Key: FOP-2639
> URL: https://issues.apache.org/jira/browse/FOP-2639
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.1
> Environment: linux, java version "1.7.0_101"
> OpenJDK Runtime Environment (IcedTea 2.6.6) (7u101-2.6.6-2~deb7u1)
> OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
>Reporter: Stefan Hegny
>Priority: Minor
> Labels: pdf/a
> Attachments: testlibertine.fo, testlibertine.pdf
>
>
> Using the font LinLibertine_R.otf from the latest 5.3 release
> (http://sourceforge.net/projects/linuxlibertine/files/linuxlibertine/5.3.0/)
> in xsl-fo and requesting PDF/A-1a conformance gives validation error on
> https://www.pdf-tools.com/pdf/pdfa-online-pruefen.aspx:
> brief_DE_letter_PG_1_ovlsame.pdf does not conform to PDF/A.
> {noformat}
> Validating file "brief_DE_letter_PG_1_ovlsame.pdf" for conformance level
> pdfa-1a
> The value of the CIDSet[2] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[3] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[4] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[5] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[6] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[7] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[8] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[9] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[10] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[11] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[12] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[25] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[28] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[29] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[30] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[31] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[32] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[33] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[44] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[45] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[50] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[55] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[57] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[58] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[59] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[60] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[61] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[62] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[63] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[64] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The document does not conform to the requested standard.
> The document contains fonts without embedded font programs or encoding
> information (CMAPs).
> {noformat}
> Will attach sample fo input file, relevant config lines are
> {{ embed-url="file:///home/hegny/temp/libertine-5.3/LinLibertine_R.otf">}}
> {{}}
> {{}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (FOP-2625) Allow Attachments for PDF/A-3
[ https://issues.apache.org/jira/browse/FOP-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Hegny closed FOP-2625. - excellent, thanks > Allow Attachments for PDF/A-3 > - > > Key: FOP-2625 > URL: https://issues.apache.org/jira/browse/FOP-2625 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.1 > Environment: probably any >Reporter: Stefan Hegny >Assignee: simon steiner >Priority: Minor > Labels: pdf, pdf/a > Fix For: trunk > > Attachments: fop.xconf, test_sampembed.fo > > > Embedded files should be allowed for PDF/A-3, e.g. required by the german > "Zugferd" invoice standard, but: > SEVERE: Exception > org.apache.fop.apps.FOPException: PDF/A-3b does not allow embedded files. > org.apache.fop.pdf.PDFConformanceException: PDF/A-3b does not allow embedded > files. > at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288) > at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) > at org.apache.fop.cli.Main.startFOP(Main.java:186) > at org.apache.fop.cli.Main.main(Main.java:217) > Caused by: org.apache.fop.pdf.PDFConformanceException: PDF/A-3b does not > allow embedded files. > at > org.apache.fop.pdf.PDFProfile.verifyEmbeddedFilesAllowed(PDFProfile.java:336) > at > org.apache.fop.render.pdf.PDFRenderingUtil.addEmbeddedFile(PDFRenderingUtil.java:651) > at > org.apache.fop.render.pdf.PDFDocumentHandler.handleExtensionObject(PDFDocumentHandler.java:318) > at > org.apache.fop.render.intermediate.util.IFDocumentHandlerProxy.handleExtensionObject(IFDocumentHandlerProxy.java:192) > at > org.apache.fop.render.intermediate.IFRenderer.processOffDocumentItem(IFRenderer.java:325) > at > org.apache.fop.area.RenderPagesModel.handleOffDocumentItem(RenderPagesModel.java:232) > at > org.apache.fop.area.AreaTreeHandler.addOffDocumentItem(AreaTreeHandler.java:376) > at > org.apache.fop.area.AreaTreeHandler.wrapAndAddExtensionAttachments(AreaTreeHandler.java:245) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2639) CIDSet error when PDF/A validating fop output with Linux Libertine OTF
[
https://issues.apache.org/jira/browse/FOP-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Hegny updated FOP-2639:
--
Attachment: testlibertine.fo
{noformat}
../fop-2.1/fop -pdfprofile PDF/A-1a -a -d -c ../conf/fop_hc_1a.xconf -fo
testlibertine.fo -pdf testlibertine.pdf
{noformat}
> CIDSet error when PDF/A validating fop output with Linux Libertine OTF
> --
>
> Key: FOP-2639
> URL: https://issues.apache.org/jira/browse/FOP-2639
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.1
> Environment: linux, java version "1.7.0_101"
> OpenJDK Runtime Environment (IcedTea 2.6.6) (7u101-2.6.6-2~deb7u1)
> OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
>Reporter: Stefan Hegny
>Priority: Minor
> Labels: pdf/a
> Attachments: testlibertine.fo
>
>
> Using the font LinLibertine_R.otf from the latest 5.3 release
> (http://sourceforge.net/projects/linuxlibertine/files/linuxlibertine/5.3.0/)
> in xsl-fo and requesting PDF/A-1a conformance gives validation error on
> https://www.pdf-tools.com/pdf/pdfa-online-pruefen.aspx:
> brief_DE_letter_PG_1_ovlsame.pdf does not conform to PDF/A.
> {noformat}
> Validating file "brief_DE_letter_PG_1_ovlsame.pdf" for conformance level
> pdfa-1a
> The value of the CIDSet[2] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[3] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[4] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[5] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[6] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[7] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[8] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[9] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[10] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[11] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[12] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[25] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[28] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[29] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[30] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[31] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[32] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[33] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[44] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[45] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[50] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[55] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[57] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[58] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[59] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[60] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[61] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[62] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[63] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The value of the CIDSet[64] of font EA+LinuxLibertineCapitalsO is false
> but must be true.
> The document does not conform to the requested standard.
> The document contains fonts without embedded font programs or encoding
> information (CMAPs).
> {noformat}
> Will attach sample fo input file, relevant config lines are
> {{ embed-url="file:///home/hegny/temp/libertine-5.3/LinLibertine_R.otf">}}
> {{}}
> {{}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FOP-2639) CIDSet error when PDF/A validating fop output with Linux Libertine OTF
Stefan Hegny created FOP-2639:
-
Summary: CIDSet error when PDF/A validating fop output with Linux
Libertine OTF
Key: FOP-2639
URL: https://issues.apache.org/jira/browse/FOP-2639
Project: FOP
Issue Type: Bug
Components: renderer/pdf
Affects Versions: 2.1
Environment: linux, java version "1.7.0_101"
OpenJDK Runtime Environment (IcedTea 2.6.6) (7u101-2.6.6-2~deb7u1)
OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
Reporter: Stefan Hegny
Priority: Minor
Using the font LinLibertine_R.otf from the latest 5.3 release
(http://sourceforge.net/projects/linuxlibertine/files/linuxlibertine/5.3.0/) in
xsl-fo and requesting PDF/A-1a conformance gives validation error on
https://www.pdf-tools.com/pdf/pdfa-online-pruefen.aspx:
brief_DE_letter_PG_1_ovlsame.pdf does not conform to PDF/A.
{noformat}
Validating file "brief_DE_letter_PG_1_ovlsame.pdf" for conformance level pdfa-1a
The value of the CIDSet[2] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[3] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[4] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[5] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[6] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[7] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[8] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[9] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[10] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[11] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[12] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[25] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[28] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[29] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[30] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[31] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[32] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[33] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[44] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[45] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[50] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[55] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[57] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[58] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[59] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[60] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[61] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[62] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[63] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The value of the CIDSet[64] of font EA+LinuxLibertineCapitalsO is false but
must be true.
The document does not conform to the requested standard.
The document contains fonts without embedded font programs or encoding
information (CMAPs).
{noformat}
Will attach sample fo input file, relevant config lines are
{{}}
{{}}
{{}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FOP-2625) Allow Attachments for PDF/A-3
[ https://issues.apache.org/jira/browse/FOP-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384238#comment-15384238 ] Stefan Hegny commented on FOP-2625: --- confirming: it works! > Allow Attachments for PDF/A-3 > - > > Key: FOP-2625 > URL: https://issues.apache.org/jira/browse/FOP-2625 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.1 > Environment: probably any >Reporter: Stefan Hegny >Assignee: simon steiner >Priority: Minor > Labels: pdf, pdf/a > Attachments: fop.xconf, test_sampembed.fo > > > Embedded files should be allowed for PDF/A-3, e.g. required by the german > "Zugferd" invoice standard, but: > SEVERE: Exception > org.apache.fop.apps.FOPException: PDF/A-3b does not allow embedded files. > org.apache.fop.pdf.PDFConformanceException: PDF/A-3b does not allow embedded > files. > at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288) > at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) > at org.apache.fop.cli.Main.startFOP(Main.java:186) > at org.apache.fop.cli.Main.main(Main.java:217) > Caused by: org.apache.fop.pdf.PDFConformanceException: PDF/A-3b does not > allow embedded files. > at > org.apache.fop.pdf.PDFProfile.verifyEmbeddedFilesAllowed(PDFProfile.java:336) > at > org.apache.fop.render.pdf.PDFRenderingUtil.addEmbeddedFile(PDFRenderingUtil.java:651) > at > org.apache.fop.render.pdf.PDFDocumentHandler.handleExtensionObject(PDFDocumentHandler.java:318) > at > org.apache.fop.render.intermediate.util.IFDocumentHandlerProxy.handleExtensionObject(IFDocumentHandlerProxy.java:192) > at > org.apache.fop.render.intermediate.IFRenderer.processOffDocumentItem(IFRenderer.java:325) > at > org.apache.fop.area.RenderPagesModel.handleOffDocumentItem(RenderPagesModel.java:232) > at > org.apache.fop.area.AreaTreeHandler.addOffDocumentItem(AreaTreeHandler.java:376) > at > org.apache.fop.area.AreaTreeHandler.wrapAndAddExtensionAttachments(AreaTreeHandler.java:245) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2625) Allow Attachments for PDF/A-3
[ https://issues.apache.org/jira/browse/FOP-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384043#comment-15384043 ] Stefan Hegny commented on FOP-2625: --- @simon steiner, PDF/A-3 is based on PDF 1.7, your fop.xconf sample states 1.4 > Allow Attachments for PDF/A-3 > - > > Key: FOP-2625 > URL: https://issues.apache.org/jira/browse/FOP-2625 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.1 > Environment: probably any >Reporter: Stefan Hegny >Assignee: simon steiner >Priority: Minor > Labels: pdf, pdf/a > Attachments: fop.xconf, test_sampembed.fo > > > Embedded files should be allowed for PDF/A-3, e.g. required by the german > "Zugferd" invoice standard, but: > SEVERE: Exception > org.apache.fop.apps.FOPException: PDF/A-3b does not allow embedded files. > org.apache.fop.pdf.PDFConformanceException: PDF/A-3b does not allow embedded > files. > at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288) > at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) > at org.apache.fop.cli.Main.startFOP(Main.java:186) > at org.apache.fop.cli.Main.main(Main.java:217) > Caused by: org.apache.fop.pdf.PDFConformanceException: PDF/A-3b does not > allow embedded files. > at > org.apache.fop.pdf.PDFProfile.verifyEmbeddedFilesAllowed(PDFProfile.java:336) > at > org.apache.fop.render.pdf.PDFRenderingUtil.addEmbeddedFile(PDFRenderingUtil.java:651) > at > org.apache.fop.render.pdf.PDFDocumentHandler.handleExtensionObject(PDFDocumentHandler.java:318) > at > org.apache.fop.render.intermediate.util.IFDocumentHandlerProxy.handleExtensionObject(IFDocumentHandlerProxy.java:192) > at > org.apache.fop.render.intermediate.IFRenderer.processOffDocumentItem(IFRenderer.java:325) > at > org.apache.fop.area.RenderPagesModel.handleOffDocumentItem(RenderPagesModel.java:232) > at > org.apache.fop.area.AreaTreeHandler.addOffDocumentItem(AreaTreeHandler.java:376) > at > org.apache.fop.area.AreaTreeHandler.wrapAndAddExtensionAttachments(AreaTreeHandler.java:245) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2625) Allow Attachments for PDF/A-3
[ https://issues.apache.org/jira/browse/FOP-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Hegny updated FOP-2625: -- Attachment: test_sampembed.fo process with -pdfprofile 'PDF/A-3a' and a config file that includes Times (e.g. Nimbus Roman from ghostscript). A quick patch is here: https://stackoverflow.com/questions/35015079/fop-pdf-a-3b-does-not-allow-embedded-files/38393673#38393673 > Allow Attachments for PDF/A-3 > - > > Key: FOP-2625 > URL: https://issues.apache.org/jira/browse/FOP-2625 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.1 > Environment: probably any >Reporter: Stefan Hegny >Priority: Minor > Labels: pdf, pdf/a > Attachments: test_sampembed.fo > > > Embedded files should be allowed for PDF/A-3, e.g. required by the german > "Zugferd" invoice standard, but: > SEVERE: Exception > org.apache.fop.apps.FOPException: PDF/A-3b does not allow embedded files. > org.apache.fop.pdf.PDFConformanceException: PDF/A-3b does not allow embedded > files. > at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288) > at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) > at org.apache.fop.cli.Main.startFOP(Main.java:186) > at org.apache.fop.cli.Main.main(Main.java:217) > Caused by: org.apache.fop.pdf.PDFConformanceException: PDF/A-3b does not > allow embedded files. > at > org.apache.fop.pdf.PDFProfile.verifyEmbeddedFilesAllowed(PDFProfile.java:336) > at > org.apache.fop.render.pdf.PDFRenderingUtil.addEmbeddedFile(PDFRenderingUtil.java:651) > at > org.apache.fop.render.pdf.PDFDocumentHandler.handleExtensionObject(PDFDocumentHandler.java:318) > at > org.apache.fop.render.intermediate.util.IFDocumentHandlerProxy.handleExtensionObject(IFDocumentHandlerProxy.java:192) > at > org.apache.fop.render.intermediate.IFRenderer.processOffDocumentItem(IFRenderer.java:325) > at > org.apache.fop.area.RenderPagesModel.handleOffDocumentItem(RenderPagesModel.java:232) > at > org.apache.fop.area.AreaTreeHandler.addOffDocumentItem(AreaTreeHandler.java:376) > at > org.apache.fop.area.AreaTreeHandler.wrapAndAddExtensionAttachments(AreaTreeHandler.java:245) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2621) ToUnicode missing for AdobeStandardEncoding Fonts but present for FontSpecific
[ https://issues.apache.org/jira/browse/FOP-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Hegny updated FOP-2621: -- Description: Generating PDF/A-1a gives non-validating pdf due to missing ToUnicode tables for embedded AdobeStandardEncoding Fonts (e.g. Nimbus Roman 9L from ghostscript, but also commercial T1 fonts). Validation here refers to the online validator at pdf-tools.com . Fonts embedded with FontSpecific Encoding produce ToUnicode tables. Using modified .afm files where AdobeStandardEncoding is manually replaced by FontSpecific will produce the ToUnicode tables for these fonts too and then the resulting PDF will validate. The Files look identical to those non-validating due to AdobeStandardEncoding also for more complex documents. fop-2.1/fop -c working.xconf -a -pdfprofile 'PDF/A-1a' -pdf test_works.pdf -fo test_0.fo fop-2.1/fop -c notworking.xconf -a -pdfprofile 'PDF/A-1a' -pdf test_notvalid.pdf -fo test_0.fo was: Generating PDF/A-1a gives non-validating pdf due to missing ToUnicode tables for embedded AdobeStandardEncoding Fonts (e.g. Nimbus Roman 9L from ghostscript, but also commercial T1 fonts). Fonts embedded with FontSpecific Encoding produce ToUnicode tables. Using modified .afm files where AdobeStandardEncoding is manually replaced by FontSpecific will produce the ToUnicode tables for these fonts too and then the resulting PDF will validate. The Files look identical to those non-validating due to AdobeStandardEncoding also for more complex documents. fop-2.1/fop -c working.xconf -a -pdfprofile 'PDF/A-1a' -pdf test_works.pdf -fo test_0.fo fop-2.1/fop -c notworking.xconf -a -pdfprofile 'PDF/A-1a' -pdf test_notvalid.pdf -fo test_0.fo Summary: ToUnicode missing for AdobeStandardEncoding Fonts but present for FontSpecific (was: ToUnicode missing for AdobeStandardEncodingFonts but present for FontSpecific) > ToUnicode missing for AdobeStandardEncoding Fonts but present for FontSpecific > -- > > Key: FOP-2621 > URL: https://issues.apache.org/jira/browse/FOP-2621 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.1 > Environment: Linux > java version "1.8.0_73" > Java(TM) SE Runtime Environment (build 1.8.0_73-b02) > Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode) > java version "1.7.0_95" > OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1) > OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode) >Reporter: Stefan Hegny >Priority: Minor > Labels: encoding, pdf/a > Attachments: buggele1.tar.gz > > > Generating PDF/A-1a gives non-validating pdf due to missing ToUnicode tables > for embedded AdobeStandardEncoding Fonts (e.g. Nimbus Roman 9L from > ghostscript, but also commercial T1 fonts). Validation here refers to the > online validator at pdf-tools.com . > Fonts embedded with FontSpecific Encoding produce ToUnicode tables. > Using modified .afm files where AdobeStandardEncoding is manually replaced by > FontSpecific will produce the ToUnicode tables for these fonts too and then > the resulting PDF will validate. The Files look identical to those > non-validating due to AdobeStandardEncoding also for more complex documents. > fop-2.1/fop -c working.xconf -a -pdfprofile 'PDF/A-1a' -pdf test_works.pdf > -fo test_0.fo > fop-2.1/fop -c notworking.xconf -a -pdfprofile 'PDF/A-1a' -pdf > test_notvalid.pdf -fo test_0.fo -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FOP-2621) ToUnicode missing for AdobeStandardEncodingFonts but present for FontSpecific
[ https://issues.apache.org/jira/browse/FOP-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Hegny updated FOP-2621: -- Attachment: buggele1.tar.gz sample fo, afm and config files > ToUnicode missing for AdobeStandardEncodingFonts but present for FontSpecific > - > > Key: FOP-2621 > URL: https://issues.apache.org/jira/browse/FOP-2621 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.1 > Environment: Linux > java version "1.8.0_73" > Java(TM) SE Runtime Environment (build 1.8.0_73-b02) > Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode) > java version "1.7.0_95" > OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1) > OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode) >Reporter: Stefan Hegny >Priority: Minor > Labels: encoding, pdf/a > Attachments: buggele1.tar.gz > > > Generating PDF/A-1a gives non-validating pdf due to missing ToUnicode tables > for embedded AdobeStandardEncoding Fonts (e.g. Nimbus Roman 9L from > ghostscript, but also commercial T1 fonts). > Fonts embedded with FontSpecific Encoding produce ToUnicode tables. > Using modified .afm files where AdobeStandardEncoding is manually replaced by > FontSpecific will produce the ToUnicode tables for these fonts too and then > the resulting PDF will validate. Will attach simple sample. > fop-2.1/fop -c working.xconf -a -pdfprofile 'PDF/A-1a' -pdf test_works.pdf > -fo test_0.fo > fop-2.1/fop -c notworking.xconf -a -pdfprofile 'PDF/A-1a' -pdf > test_notvalid.pdf -fo test_0.fo -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FOP-2621) ToUnicode missing for AdobeStandardEncodingFonts but present for FontSpecific
Stefan Hegny created FOP-2621: - Summary: ToUnicode missing for AdobeStandardEncodingFonts but present for FontSpecific Key: FOP-2621 URL: https://issues.apache.org/jira/browse/FOP-2621 Project: FOP Issue Type: Bug Components: renderer/pdf Affects Versions: 2.1 Environment: Linux java version "1.8.0_73" Java(TM) SE Runtime Environment (build 1.8.0_73-b02) Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode) java version "1.7.0_95" OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1) OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode) Reporter: Stefan Hegny Priority: Minor Generating PDF/A-1a gives non-validating pdf due to missing ToUnicode tables for embedded AdobeStandardEncoding Fonts (e.g. Nimbus Roman 9L from ghostscript, but also commercial T1 fonts). Fonts embedded with FontSpecific Encoding produce ToUnicode tables. Using modified .afm files where AdobeStandardEncoding is manually replaced by FontSpecific will produce the ToUnicode tables for these fonts too and then the resulting PDF will validate. Will attach simple sample. fop-2.1/fop -c working.xconf -a -pdfprofile 'PDF/A-1a' -pdf test_works.pdf -fo test_0.fo fop-2.1/fop -c notworking.xconf -a -pdfprofile 'PDF/A-1a' -pdf test_notvalid.pdf -fo test_0.fo -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FOP-2618) Table breaks PDF/A-1 compat when accessibility requested
[
https://issues.apache.org/jira/browse/FOP-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15355284#comment-15355284
]
Stefan Hegny commented on FOP-2618:
---
Excellent, thanks a lot simon for pointing that out. I thought it would
automatically choose 1.4 if PDF/A is requested.
> Table breaks PDF/A-1 compat when accessibility requested
>
>
> Key: FOP-2618
> URL: https://issues.apache.org/jira/browse/FOP-2618
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.1
> Environment: java version "1.7.0_95"
> Linux: OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1)
> OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
> as well as Linux:
> java version "1.8.0_73"
> Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)
>Reporter: Stefan Hegny
>Priority: Minor
> Fix For: 1.1
>
>
> When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output
> of the following file will not validate on various engines (e.g. pdfbox
> preflight) with an error {{1.4 : Trailer Syntax error, /XRef cross reference
> streams are not allowed}}
> If the fo:table is taken out of the fo then it gives (more) valid output
> (i.e. not the xref error). It also avoids the xref error when specifying
> {{-pdfprofile 'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1
> with {{-a -pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed
> e.g. with exiftool) but will NOT produce the XRef Trailer syntax error.
> {{
> http://www.w3.org/1999/XSL/Format;
> xmlns:h="http://xmlns.dummycompany.com/letters;
> xmlns:hx="http://xmlns.dummycompany.com/letters/intern;
> xmlns:l="http://www.w3.org/1999/xhtml;
> xmlns:xalan="http://xml.apache.org/xalan; xml:lang="de">
>
> margin-left="10mm" margin-bottom="20mm" margin-top="32mm" page-width="21cm"
> page-height="29.6984848098cm">
>
>
>
>
>
> master-reference="first"/>
>
>
>
>
>
> border-width="0pt" padding="0mm">
> font-family="serif" font-size="11pt" space-before="28pt" font-weight="bold">
> Rechnung Nr. 2016-413
>
> font-family="serif" font-size="11pt">
>
>
>
>
>
>
>
> font-weight="bold">Leistung
>
>
> font-weight="bold">Anzahl
>
>
> text-align="end">Betrag
>
>
>
>
>
>
> Spaxschrauben 2,5x5mm
>
>
> text-align="center">100
>
>
>
> 33,75 €
>
>
>
> border-top-style="solid" position="relative" margin-top="10pt">
>
> Nettosumme
>
>
>
>
>
>
> 33,75 €
>
>
>
>
>
>
>
>
>
> }}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FOP-2618) Table breaks PDF/A-1 compat when accessibility requested
[
https://issues.apache.org/jira/browse/FOP-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15355209#comment-15355209
]
Stefan Hegny commented on FOP-2618:
---
It seems to avoid the xref error when i remove the {{role="TH"}} from the if
intermediate format and use {{-ifin}} with that modified file.
> Table breaks PDF/A-1 compat when accessibility requested
>
>
> Key: FOP-2618
> URL: https://issues.apache.org/jira/browse/FOP-2618
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.1
> Environment: java version "1.7.0_95"
> Linux: OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1)
> OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
> as well as Linux:
> java version "1.8.0_73"
> Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)
>Reporter: Stefan Hegny
>Priority: Minor
> Fix For: 1.1
>
>
> When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output
> of the following file will not validate on various engines (e.g. pdfbox
> preflight) with an error {{1.4 : Trailer Syntax error, /XRef cross reference
> streams are not allowed}}
> If the fo:table is taken out of the fo then it gives (more) valid output
> (i.e. not the xref error). It also avoids the xref error when specifying
> {{-pdfprofile 'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1
> with {{-a -pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed
> e.g. with exiftool) but will NOT produce the XRef Trailer syntax error.
> {{
> http://www.w3.org/1999/XSL/Format;
> xmlns:h="http://xmlns.dummycompany.com/letters;
> xmlns:hx="http://xmlns.dummycompany.com/letters/intern;
> xmlns:l="http://www.w3.org/1999/xhtml;
> xmlns:xalan="http://xml.apache.org/xalan; xml:lang="de">
>
> margin-left="10mm" margin-bottom="20mm" margin-top="32mm" page-width="21cm"
> page-height="29.6984848098cm">
>
>
>
>
>
> master-reference="first"/>
>
>
>
>
>
> border-width="0pt" padding="0mm">
> font-family="serif" font-size="11pt" space-before="28pt" font-weight="bold">
> Rechnung Nr. 2016-413
>
> font-family="serif" font-size="11pt">
>
>
>
>
>
>
>
> font-weight="bold">Leistung
>
>
> font-weight="bold">Anzahl
>
>
> text-align="end">Betrag
>
>
>
>
>
>
> Spaxschrauben 2,5x5mm
>
>
> text-align="center">100
>
>
>
> 33,75 €
>
>
>
> border-top-style="solid" position="relative" margin-top="10pt">
>
> Nettosumme
>
>
>
>
>
>
> 33,75 €
>
>
>
>
>
>
>
>
>
> }}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FOP-2618) Table breaks PDF/A-1 compat when accessibility requested
[
https://issues.apache.org/jira/browse/FOP-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Hegny updated FOP-2618:
--
Summary: Table breaks PDF/A-1 compat when accessibility requested (was:
Table breaks PDF/A-1a compat by adding XRef)
> Table breaks PDF/A-1 compat when accessibility requested
>
>
> Key: FOP-2618
> URL: https://issues.apache.org/jira/browse/FOP-2618
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.1
> Environment: java version "1.7.0_95"
> Linux: OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1)
> OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
> as well as Linux:
> java version "1.8.0_73"
> Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)
>Reporter: Stefan Hegny
>Priority: Minor
> Fix For: 1.1
>
>
> When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output
> of the following file will not validate on various engines (e.g. pdfbox
> preflight) with an error {{1.4 : Trailer Syntax error, /XRef cross reference
> streams are not allowed}}
> If the fo:table is taken out of the fo then it gives (more) valid output
> (i.e. not the xref error). It also avoids the xref error when specifying
> {{-pdfprofile 'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1
> with {{-a -pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed
> e.g. with exiftool) but will NOT produce the XRef Trailer syntax error.
> {{
> http://www.w3.org/1999/XSL/Format;
> xmlns:h="http://xmlns.dummycompany.com/letters;
> xmlns:hx="http://xmlns.dummycompany.com/letters/intern;
> xmlns:l="http://www.w3.org/1999/xhtml;
> xmlns:xalan="http://xml.apache.org/xalan; xml:lang="de">
>
> margin-left="10mm" margin-bottom="20mm" margin-top="32mm" page-width="21cm"
> page-height="29.6984848098cm">
>
>
>
>
>
> master-reference="first"/>
>
>
>
>
>
> border-width="0pt" padding="0mm">
> font-family="serif" font-size="11pt" space-before="28pt" font-weight="bold">
> Rechnung Nr. 2016-413
>
> font-family="serif" font-size="11pt">
>
>
>
>
>
>
>
> font-weight="bold">Leistung
>
>
> font-weight="bold">Anzahl
>
>
> text-align="end">Betrag
>
>
>
>
>
>
> Spaxschrauben 2,5x5mm
>
>
> text-align="center">100
>
>
>
> 33,75 €
>
>
>
> border-top-style="solid" position="relative" margin-top="10pt">
>
> Nettosumme
>
>
>
>
>
>
> 33,75 €
>
>
>
>
>
>
>
>
>
> }}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FOP-2618) Table breaks PDF/A-1a compat by adding XRef
[
https://issues.apache.org/jira/browse/FOP-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Hegny updated FOP-2618:
--
Description:
When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output of
the following file will not validate on various engines (e.g. pdfbox preflight)
with an error {{1.4 : Trailer Syntax error, /XRef cross reference streams are
not allowed}}
If the fo:table is taken out of the fo then it gives (more) valid output (i.e.
not the xref error). It also avoids the xref error when specifying
{{-pdfprofile 'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1 with
{{-a -pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed e.g.
with exiftool) but will NOT produce the XRef Trailer syntax error.
{{
http://www.w3.org/1999/XSL/Format;
xmlns:h="http://xmlns.dummycompany.com/letters;
xmlns:hx="http://xmlns.dummycompany.com/letters/intern;
xmlns:l="http://www.w3.org/1999/xhtml;
xmlns:xalan="http://xml.apache.org/xalan; xml:lang="de">
Rechnung Nr. 2016-413
Leistung
Anzahl
Betrag
Spaxschrauben 2,5x5mm
100
33,75 €
Nettosumme
33,75 €
}}
was:
When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output of
the following file will not validate on various engines (e.g. pdfbox preflight)
with an error {{1.4 : Trailer Syntax error, /XRef cross reference streams are
not allowed}}
If the table is taken out of the fo then it gives (more) valid output (i.e. not
the xref error). It also avoids the xref error when specifying {{-pdfprofile
'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1 with {{-a
-pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed e.g. with
exiftool) but will NOT produce the XRef Trailer syntax error.
{{
http://www.w3.org/1999/XSL/Format;
xmlns:h="http://xmlns.dummycompany.com/letters;
xmlns:hx="http://xmlns.dummycompany.com/letters/intern;
xmlns:l="http://www.w3.org/1999/xhtml;
xmlns:xalan="http://xml.apache.org/xalan; xml:lang="de">
Rechnung Nr. 2016-413
Leistung
Anzahl
Betrag
Spaxschrauben 2,5x5mm
100
33,75 €
[jira] [Updated] (FOP-2618) Table break PDF/A-1a by adding XRef
[
https://issues.apache.org/jira/browse/FOP-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Hegny updated FOP-2618:
--
Description:
When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output of
the following file will not validate on various engines (e.g. pdfbox preflight)
with an error {{1.4 : Trailer Syntax error, /XRef cross reference streams are
not allowed}}
If the table is taken out of the fo then it gives (more) valid output (i.e. not
the xref error). It also avoids the xref error when specifying {{-pdfprofile
'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1 with {{-a
-pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed e.g. with
exiftool) but will NOT produce the XRef Trailer syntax error.
{{
http://www.w3.org/1999/XSL/Format;
xmlns:h="http://xmlns.dummycompany.com/letters;
xmlns:hx="http://xmlns.dummycompany.com/letters/intern;
xmlns:l="http://www.w3.org/1999/xhtml;
xmlns:xalan="http://xml.apache.org/xalan; xml:lang="de">
Rechnung Nr. 2016-413
Leistung
Anzahl
Betrag
Spaxschrauben 2,5x5mm
100
33,75 €
Nettosumme
33,75 €
}}
was:
When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output of
the following file will not validate on various engines (e.g. pdfbox preflight)
with an error {{1.4 : Trailer Syntax error, /XRef cross reference streams are
not allowed}}
If the table is taken out of the fo then it gives (more) valid output (i.e. not
the xref error). It also avoids the xref error when specifying {{-pdfprofile
'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1 with {{-a
-pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed e.g. with
exiftool) but will NOT produce the XRef Trailer syntax error.
{{
http://www.w3.org/1999/XSL/Format;
xmlns:h="http://xmlns.dummycompany.com/letters;
xmlns:hx="http://xmlns.dummycompany.com/letters/intern;
xmlns:l="http://www.w3.org/1999/xhtml;
xmlns:xalan="http://xml.apache.org/xalan; xml:lang="de">
Rechnung Nr. 2016-413
Leistung
Anzahl
Betrag
Spaxschrauben 2,5x5mm
100
33,75 €
[jira] [Created] (FOP-2618) Table break PDF/A-1a by adding XRef
Stefan Hegny created FOP-2618:
-
Summary: Table break PDF/A-1a by adding XRef
Key: FOP-2618
URL: https://issues.apache.org/jira/browse/FOP-2618
Project: FOP
Issue Type: Bug
Components: renderer/pdf
Affects Versions: 2.1
Environment: java version "1.7.0_95"
Linux: OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1~deb7u1)
OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
as well as Linux:
java version "1.8.0_73"
Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)
Reporter: Stefan Hegny
Priority: Minor
Fix For: 1.1
When running fop 2.1 with {{-a -pdfprofile 'PDF/A-1a'}} then the pdf output of
the following file will not validate on various engines (e.g. pdfbox preflight)
with an error {{1.4 : Trailer Syntax error, /XRef cross reference streams are
not allowed}}
If the table is taken out of the fo then it gives (more) valid output (i.e. not
the xref error). It also avoids the xref error when specifying {{-pdfprofile
'PDF/A-1b'}} and no {{-a}} flag with fop 2.1. Using fop 1.1 with {{-a
-pdfprofile 'PDF/A-1a'}} will give other issues (that can be fixed e.g. with
exiftool) but will NOT produce the XRef Trailer syntax error.
{{
http://www.w3.org/1999/XSL/Format;
xmlns:h="http://xmlns.dummycompany.com/letters;
xmlns:hx="http://xmlns.dummycompany.com/letters/intern;
xmlns:l="http://www.w3.org/1999/xhtml;
xmlns:xalan="http://xml.apache.org/xalan; xml:lang="de">
Rechnung Nr. 2016-413
Leistung
Anzahl
Betrag
Spaxschrauben 2,5x5mm
100
33,75 €
Nettosumme
33,75 €
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
