Skip to content

Add PDF/A-4 (ISO 19005-4) - #17

Merged
MPCoreDeveloper merged 2 commits into
mainfrom
feat/10-pdf-a-4
Nov 14, 2026
Merged

MPCoreDeveloper merged 2 commits into
mainfrom
feat/10-pdf-a-4

Conversation

@MPCoreDeveloper

Copy link
Copy Markdown
Owner

Summary

Closes #10 by adding the one profile that was genuinely missing: PDF/A-4 (ISO 19005-4). PDF/A-2u and -3u were already shipped in 1.6.0 and are unchanged; this PR verifies them with the same CI run and adds the PDF 2.0 base level.

  • PdfAProfile.PdfA4 — the base level of ISO 19005-4.
  • PdfAProfileRules — part 4, PDF 2.0, no conformance level, transparency allowed, embedded files refused.
  • XmpPacket — writes pdfaid:part 4 and no pdfaid:conformance element for the base level.
  • ArchiveExamples — writes archive-4.pdf and archive-source-4.pdf beside the other five profiles.
  • compliance.yml — the veraPDF loop now includes 4; the cross-validators (PDFBox 3.0.8, Ghostscript) have no PDF/A-4 mode, which the workflow states.
  • Manual chapter 24 lists the six profiles and explains the missing conformance element.

Evidence

  • Local: archive-4.pdf is %PDF-2.0, pdfaid:part = 4, no pdfaid:conformance, one output intent, qpdf check: no problems, 6 streams decoded, 0 failed.
  • Tests: 1196 passed / 0 failed / 0 skipped on net10.0 and net11.0, including the new PDF/A-4 row in Writes_the_structures_the_profile_requires.
  • veraPDF: the Validate the archival output job in compliance.yml validates archive-4.pdf and archive-source-4.pdf with veraPDF 1.30.4 on this PR; the run is the conformance evidence (this library never claims conformance itself).
  • Manual: 125 pages, check: ok.

Out of scope

PDF/A-4f (arbitrary attachments) and PDF/A-4u (Unicode), and level A. The base PDF/A-4 refuses embedded files, which the requirements analysis enforces.

Closes #10.

PdfAProfile.PdfA4 writes a PDF 2.0 document with pdfaid:part 4 and no conformance element — the base level of ISO 19005-4 — with the embedded fonts, sRGB output intent and transparency the other profiles already allow. PDF/A-2u and -3u were already shipped in 1.6.0 and stay as they are.

The archive example writes archive-4.pdf and archive-source-4.pdf, compliance.yml validates them with veraPDF, and the manual's chapter 24 lists the new profile. The cross-validators have no PDF/A-4 mode, which the workflow now states.

Tests: 1196 passed on both legs. Closes #10.
veraPDF PDF/A-4 rejects two things the first draft wrote: pdfaid:rev must be 2020, and the document information dictionary is forbidden (a trailer /Info is allowed only beside a catalog /PieceInfo). The packet now carries the revision year, and a PDF/A-4 conversion writes no Info dictionary at all — the packet is the only copy, which is what ISO 19005-4 asks for.

The three rules (6.1.3-4, 6.1.3-5, 6.7.3-5) were read from the failed compliance report, not guessed.
@MPCoreDeveloper
MPCoreDeveloper merged commit 9aae341 into main Nov 14, 2026
6 checks passed
@MPCoreDeveloper
MPCoreDeveloper deleted the feat/10-pdf-a-4 branch November 14, 2026 19:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Decision] PDF/A-2u/-3u/-4 beyond the current claim (P5)

1 participant