SaveAsPdfE method

Esta entrada API preserva identificadores, assinaturas, blocos de código e termos PDF em sua forma original.

Saves the current document as a PDF/E-1 conformant file by post-processing the base PDF with an incremental update that injects PDF/E-1 file-format markers (ISO 24517-1:2008).

SaveAsPdfE performs the regular SaveAs first, then layers an incremental update on top of the saved bytes that promotes the file to a PDF/E-1 archive (ISO 24517-1:2008, the engineering document format derived from PDF 1.6). The post-processing injects four classes of markers into the saved stream:

• An XMP metadata stream that declares PDF/E identification (pdfe:ISO_PDFEVersion = "PDF/E-1") plus the matching pdfaExtension:schemas description for the pdfe namespace, and bridged Dublin Core / xmp / pdf properties inherited from ISO 19005-1 §6.7 via §13.1 (dc:title / dc:creator / dc:description / xmp:CreateDate / xmp:ModifyDate / xmp:MetadataDate / xmp:CreatorTool / pdf:Producer / pdf:Keywords).
• A rewritten Document Information Dictionary that adds the mandatory /ISO_PDFEVersion (PDF/E-1) entry required by §5 SHALL clause. The Info object keeps its original object number; PDFium-emitted Info entries are preserved untouched. When the source trailer carries no /Info, a fresh Info dictionary is synthesised and a new /Info reference is written into the trailer.
• An updated document catalog with a /Metadata reference pointing to the new XMP stream.
• A trailer /ID array (§6.2): reused from FPDF_GetFileIdentifier when the source PDF already carries one, otherwise derived deterministically from the source bytes.

The output stays byte-identical to the base SaveAs result up to the end of the original PDF; only the incremental update is appended. Existing readers that don't understand PDF/E still render the file exactly as the regular SaveAs would. The two overloads differ only in how the configuration is passed in: the file-name-only form uses TPdfESaveOptions.Default with auto-population from FPDF_GetMetaText and FPDF_GetFileIdentifier, while the TPdfESaveOptions form lets the caller override Title, Author, Subject, Keywords, Creator, Producer, CreationDate, ModDate, DocumentId, InstanceId, and the Version string (defaults to "PDF/E-1").

Returns True on success. Returns False if the base SaveAs failed or if the incremental update could not be attached (typically an invalid trailer in the saved bytes).

• SaveAsPdfE attaches the file-format markers required by ISO 24517-1 — it does not embed missing fonts, strip prohibited XObjects, normalise ExtGState keys, or remove XFA forms. Authoring a document whose content already meets PDF/E-1 (per §7–§11) is still the caller's responsibility. Use ValidatePdfE to surface the file-format-level issues this method addresses; pair with an external PDF/E validator (callas pdfaPilot, axesPDF, ...) for content-level checks.
• Unlike PDF/A and PDF/UA, PDF/E-1 permits encryption (§6.3). When the source is encrypted, the trailer /ID array and the strings inside it must be direct objects; SaveAsPdfE writes the /ID directly, satisfying that constraint.
• Info-dictionary rewriting is the first time PDFiumVCL's PDF/x pipeline modifies an existing Info object. The new Info dictionary uses the same object number as the source, so xref / trailer /Info references remain valid.
• The pdfe namespace URI used by this implementation is http://www.aiim.org/pdfe/ns/id/ (AIIM industry convention, matching pdfa / pdfua URIs). The text of ISO 24517-1:2008 §13.3 prints this URI without one of the "i" letters, which appears to be a typo. Override via TPdfESaveOptions.Version if a validator demands the strict-spec spelling.

SaveAsPdfEToStream, ValidatePdfE, PdfEConformance, SaveAsPdfA, SaveAsPdfUa