https://bugs.documentfoundation.org/show_bug.cgi?id=174248
Bug ID: 174248
Summary: PDF export should optionally write a machine-readable
report of the conversion
Product: LibreOffice
Version: 27.2.0.0 alpha0+ master
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: enhancement
Priority: medium
Component: Printing and PDF export
Assignee: [email protected]
Reporter: [email protected]
Description:
Headless PDF conversion (soffice --convert-to pdf) reports success or failure,
but nothing structured about the result: scripts that convert in bulk cannot
check the page count, the PDF version produced, whether the output is tagged or
PDF/UA, or which fonts were embedded, without re-opening and parsing the PDF
with separate tools.
The proposal is an opt-in JSON report: when the environment variable
LO_PDF_EXPORT_REPORT is set, the export writes a sidecar file
"<output>.report.json" next to the exported PDF carrying the output
path, page count, PDF version, tagged and PDF/UA flags, the
SOURCE_DATE_EPOCH value in effect, and the embedded font family names.
Unset, nothing changes.
A patch implementing this is in review:
https://gerrit.libreoffice.org/c/core/+/213279
Steps to Reproduce:
(1) Convert a document headlessly: soffice --convert-to pdf.
(2) Look for structured information about the result (page count, PDF version,
tagged / PDF/UA status, embedded fonts) without re-opening the PDF.
Actual Results:
Conversion reports only success or failure. Scripts that
convert in bulk must re-open and parse the PDF with separate tools
to check any of those properties.
Expected Results:
When the environment variable LO_PDF_EXPORT_REPORT is
set, the export writes a sidecar "<output>.report.json" carrying the
output path, page count, PDF version, tagged and PDF/UA flags, the
SOURCE_DATE_EPOCH value in effect, and the embedded font family
names. Unset, nothing changes.
Reproducible: Always
User Profile Reset: No
Additional Info:
Patch in review:
https://gerrit.libreoffice.org/c/core/+/213279 — filed at the Gerrit
reviewer's request.
--
You are receiving this mail because:
You are the assignee for the bug.
