[
https://issues.apache.org/jira/browse/FOP-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787065#comment-17787065
]
João André Gonçalves edited comment on FOP-3144 at 11/17/23 7:22 AM:
---------------------------------------------------------------------
[~fugerit]
I found this as part of the introduction of ISO-14289
_PDF/UA is intended_
_as a companion standard, to be used in conjunction with ISO 32000, ISO 19005,
ISO 15930 and other_
_standards as may apply for the purpose of achieving accessibility or as
mandated by this International_
_Standard_
All my research into this confirmed what I quoted above. I found a company
saying they can generate PDF/A and PDF/UA compliant PDFs
([BPO*|https://bfo.com/viewtext/blog/articles/pdf-ua/StructuredPDF.java]).
When comparing a FOP generated PDF/A and PDF/UA file and one using the code
above, we can see that the second file adds an extra Description element
mentioning a schema. When moving that element to the FOP generated PDF the
warning vanishes.
I'm going to try and add something to FOP so it adds that element automatically.
was (Author: JIRAUSER302961):
[~fugerit]
I found this as part of the introduction of ISO-14289
_PDF/UA is intended_
_as a companion standard, to be used in conjunction with ISO 32000, ISO 19005,
ISO 15930 and other_
_standards as may apply for the purpose of achieving accessibility or as
mandated by this International_
_Standard_
All my research into this confirmed what I quoted above. I found a company
saying they can generate PDF/A and PDF/UA compliant PDFs
([BPO*|https://bfo.com/viewtext/blog/articles/pdf-ua/StructuredPDF.java])
When comparing a FOP generated PDF/A and PDF/UA file and one using the code
above, we can see that the second file adds an extra Description element
mentioning a schema. When moving that element to the FOP generated PDF the
warning vanishes.
I'm going to try and add something to FOP so it adds that element automatically.
> 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
> Priority: Major
>
> 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)
