4 people e4cd9e2557 PDF/A: no sRGB output intent for CMYK documents, and pdfa_verify checks the intent's colour space (#667) (#732) ...

* PDF/A: no sRGB output intent for CMYK documents, and verify checks the intent's colour space (#667)

pdfa_convert always added an sRGB output intent when there was none,
even for documents whose only content is DeviceCMYK, and pdfa_verify
then called them compliant: it only checked that some PDF/A output
intent existed. ISO 19005-2 6.2.4.3 allows DeviceCMYK only with a CMYK
output intent, and DeviceRGB only with an RGB one.

- verify reads the PDF/A output intent's destination profile (/N, else
  the ICC header's data colour space) and reports DeviceCMYK under a
  non-CMYK intent and DeviceRGB under a non-RGB one (6.2.4.3, not
  fixable).
- convert adds the generated sRGB intent only when the document has no
  DeviceCMYK; a CMYK document keeps the existing "needs a CMYK output
  intent (not added automatically)" issue instead of a wrong intent.
- Device colour detection tells gray, RGB and CMYK apart (gray works
  under any intent).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* PDF/A: DefaultRGB/DefaultCMYK resources satisfy the output-intent colour check

ISO 19005-2 6.2.4.3 accepts device colour drawn through a default colour space under any output
intent.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: DWAA1660 <DWAA1660@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Brandon Thomas <echelon@gmail.com>

2026-10-10 06:22:47 -04:00

..

src

PDF/A: no sRGB output intent for CMYK documents, and pdfa_verify checks the intent's colour space (#667) (#732)

2026-10-10 06:22:47 -04:00

Cargo.toml

Rename PrintCraft to PdfCraft (#174)

2026-10-07 16:03:57 -04:00