PdfProcessing: Generated PDF files are not PDF/A compliant according to some validation tools
When opened in Adobe Reader it says that the file "claims compliance". However, when verifying the compliance with some validation tools there seem to be some issues mainly related but not limited to fonts.
I would like to add that the title of this bug is somewhat misleading. From our tests, it appears that RadPdfProcessing is not producing PDF/A (1B) compliant documents.
The same source pdf document can be saved in the Adobe suite as PDF/A 1B compliant and will pass verification of veraPDF (and be consumed without issue by another application expecting a compliant document), while the output of RadPdfProcessing does not pass verification and is not consumed by the same application.
Also note that the source document is a PDF originally generated from a Telerik RadDocument then imported and re-exported through the RadFixedDocument. So, it doesn't appear there is an end-to-end solution for generating a compliant document using only Telerik tools.
In my opinion, this should escalate the urgency under which this issue is addressed.
See support ticket 1349612 for a sample application.
I'm willing to test some pre-release bits should you need help with that.
Thanks for listening!
Posted on:13 Feb 2018 14:57
Hi Mi Ha,
Thank you for the suggestion. I am adding it to the internal information for the item so the team can consider it when working on this task.
Posted on:10 Feb 2018 10:26
Please validate against http://verapdf.org/.
Quote from the website:
veraPDF is a purpose-built, open source, file-format validator covering all PDF/A parts and conformance levels.
veraPDF is designed to meet the needs of digital preservationists and is supported by the PDF software developer community.