Skip to content
Lamina PDF

profile-version-conflict

All codes

  • Type: error
  • Kind: usage (the caller misused the API)

What happened

BuildOptions::with_version(PdfVersion::V2_0) was combined with a conformance profile (BuildOptions::with_profile) that is built on PDF 1.7. Builder::finish wrote nothing.

Why

The PDF/UA-1 standard for accessible PDF (ISO 14289-1) and the PDF/A-2 and PDF/A-3 archival standards (ISO 19005-2 and -3) build their rules on ISO 32000-1, which is PDF 1.7. A file that says it is PDF 2.0 can’t conform to them. Validators such as veraPDF, the open-source PDF/A and PDF/UA validator, check the header first.

How to fix

Leave the version at its default, 1.7 (or choose a lower one: the builder raises it to what the content needs). PDF 2.0 has its own profiles, PDF/A-4 and PDF/UA-2, which Lamina PDF doesn’t write yet.

Example

let options = BuildOptions::default()
    .with_version(PdfVersion::V2_0)
    .with_profile(Profile::PdfA2b);
Builder::new(options).finish()?; // profile-version-conflict

Data fields

  • profile: the profile, such as PDF/A-2b.