PDFAMode

This property enables PDF/A support.

Values: wpdfaOff, wpdfaLevelA or wpdfaLevelB

PDF/A is a new norm which based on PDF 1.4 - it was created to provide a guideline for the creation of document files which stay readable for the time to come. So the major demand for PDF/A compliant files is that the used font files are embedded. Security measures are forbidden in PDF/A compliant files as are links to external files.

But there is more to PDF/A. We have checked the component carefully against the final documentation of PDF/A.

When you use WPTools 5 or WPTools 6 with wPDF to create the PDF files additional (invisible) tags will be added to the PDF data. This tags make it possible to identify layout elements (such as header or footer texts) on a page. They can be also used by a PDF reader to convert the PDF data into text paragraphs, something which is otherwise at least difficult and impossible if a paragraph spans a page. The wPDF engine will also create tags to mark table cells.

To activate the PDF layout tags when exporting from WPTools increment the variable Memo._WPDFParRun:

  inc(WPRichText1.Memo._WPDFParRun);

  WPPDFExport1.PDFAMode := wpdfaLevelA;

  WPPDFExport1.Print;

wPDF4 will also add the document information as XMP data to the PDF file.

wpdfaLevelB differs only little from wpdfaLevelA:

- not's add ToUnicode CMAP information

- don't force PDF tagging

Please note:

According to ISO 19005 - Chapter 6.3.8 Fonts require character mapping information. Such a table is always added, for CidFonts and also if the encoding of a font is "Difference". So the requirement 6.3.8 is met, although some PDFA validators seem to ignore the existence of the date referenced by the ToUnicode tag..

When PDF/A has been selected a sRGB color profile will be added to the document.