[ https://issues.apache.org/jira/browse/FOP-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Steiner reassigned FOP-3144: ---------------------------------- Assignee: Simon Steiner > [PATCH] Is it possible to create a PDF which is both PDF/A and PDF/UA > compliant? > -------------------------------------------------------------------------------- > > Key: FOP-3144 > URL: https://issues.apache.org/jira/browse/FOP-3144 > Project: FOP > Issue Type: Improvement > Components: renderer/pdf > Affects Versions: 2.8 > Reporter: Matteo Franci > Assignee: Simon Steiner > Priority: Major > Attachments: commons.patch, fonts.fo, fop.patch, pdfFop.xconf, > pdfUaFonts.pdf > > > I would like to create a PDF which have both a PDF/A and PDF/UA profile > active. > It seems validators do not accept the generated property : > {code:java} > <rdf:Description xmlns:pdfuaid="http://www.aiim.org/pdfua/ns/id/" > rdf:about=""> > <pdfuaid:part>1</pdfuaid:part> > </rdf:Description> {code} > So maybe the issue is not with FOP but with the compatibility of the two > standards or with the validators. > Do you have any clues about it? > I tried a few configurations, for example : > > {code:java} > <renderer mime="application/pdf"> > <pdf-ua-mode>PDF/UA-1</pdf-ua-mode> > <pdf-a-mode>PDF/A-1a</pdf-a-mode> > <version>1.4</version> > ... > </renderer> > {code} > Or > {code:java} > <renderer mime="application/pdf"> > <pdf-ua-mode>PDF/UA-1</pdf-ua-mode> > <pdf-a-mode>PDF/A-2a</pdf-a-mode> > <version>1.7</version> > ... > </renderer> > {code} > The PDF/UA validation succeds (I tried [https://check.axes4.com/en/]), > but the PDF/A validation fails (I tried adobe and > [https://avepdf.com/en/pdfa-validation] > [),|https://avepdf.com/en/pdfa-validation] with this error : > > {color:#ff0000}XMP property pdfuaid:part not defined in current schema.{color} > > Thanks in advance. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)