Bug 140663 - Please implement PDF/UA-1 conformance to PDF Export
Summary: Please implement PDF/UA-1 conformance to PDF Export
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-25 11:10 UTC by Wahrendorff
Modified: 2021-03-01 17:16 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wahrendorff 2021-02-25 11:10:20 UTC
My company is using Libreoffice as Reporting Engine to generate multiple PDF Documents for its endusers.

Now there are regulations for official Documents to be accessible. Due to lacking knowledge, people creating the templates for these Reports, tent to test their documents against PAC3 (Accessibility Checker) but since this tests for PDF/UA-1 Conformance, LibreOffice generated Documents seem to be not sufficiantly accessible to the enduser.

Please enhance your PDF-Exporteur to be able to generate PDF/UA-1 compliant Documents, as this is becoming more and more a legal requirement for PDF files in educational and governmental sectors.

Thank you.
Comment 1 Ming Hua 2021-02-26 03:34:24 UTC
LibreOffice version 7.0 or later already has experimental support for PDF/UA-1, please follow the instructions in https://wiki.documentfoundation.org/ReleaseNotes/7.0#Accessibility_improvements to enable and use it.

Does this satisfy the need of your company?
Comment 2 Wahrendorff 2021-02-26 13:02:52 UTC
Thanks, this is great news to us.

We use the UNO API to convert and export odt to pdf.

But how are the internal Filter Properties for PDF/UA named, so I can activate them via UNO?

And how would I enable the experimental features via UNO on a headless soffice process? Is there a startup parameter, maybe?
Comment 3 V Stuart Foote 2021-02-26 19:40:43 UTC
@Tomaž, any insight on UNO use of the PDF/UA-1 validator?
Comment 4 himajin100000 2021-02-26 20:01:53 UTC
1. Actually I'm not so sure which commit introduced PDF/UA "only in "Experimental Mode" only. at least, with master(7.2) build, the checkbox is visible regardless of whether Experimental Mode is on or off.

2. to use in UNO API, I believe we need to specify "PDFUACompliance" as an element of the filter data (array of PropertyValue)

https://opengrok.libreoffice.org/xref/core/filter/source/pdf/pdffilter.cxx?r=042033f1#86
https://opengrok.libreoffice.org/xref/core/filter/source/pdf/pdffilter.cxx?r=042033f1#127
https://opengrok.libreoffice.org/s?defs=GetFilterData&project=core

FWIW,
https://api.libreoffice.org/docs/idl/ref/servicecom_1_1sun_1_1star_1_1document_1_1MediaDescriptor.html#af841b998ee42c081965e62af46019fd4
https://api.libreoffice.org/docs/idl/ref/servicecom_1_1sun_1_1star_1_1document_1_1MediaDescriptor.html#a5f54aacbb0dcabe55b57487d58abc4f9
Comment 5 himajin100000 2021-02-26 20:02:37 UTC
typo : "only in "Experimental Mode" only.

-> "Experimental Mode" only
Comment 6 Tomaz Vajngerl 2021-02-27 00:15:03 UTC
It was experimental in LO 7.0, but is a standard feature in 7.1
Comment 7 Wahrendorff 2021-03-01 17:16:45 UTC
The built-in Accessibility Checker is quite awesome and unique. Very good work, guys!

I upgraded to 7.1 and implemented optional PDFUACompliance in our Reporting Tool. It works as expected!

Thank you all for your time and effort, this is exactly what is needed. Great work!