PDF/UA-1 rule reference › clause 7.21.6

PDF/UA-1 rule 7.21.6-3: A symbolic TrueType font specifies an Encoding entry in its dictionary

Not fixed automatically font

What veraPDF reports

A symbolic TrueType font specifies an Encoding entry in its dictionary

veraPDF rule 7.21.6-3 = ISO 14289-1:2014 clause 7.21.6, test 3, checked on PDF object PDTrueTypeFont.

What the requirement says

Symbolic TrueType fonts shall not contain an Encoding entry in the font dictionary

Can it be fixed automatically?

How to fix it by hand

Fonts are fixed at the source: export the PDF again from the authoring application with all fonts embedded (most office tools have an “embed fonts” or PDF/A option), or use a preflight tool that embeds missing fonts. Editing the PDF metadata does not change fonts.

Check your PDF now (free)

Upload the PDF: veraPDF lists every failed PDF/UA-1 rule, our fix runs, and veraPDF checks the fixed file again — you see “N failed rules before → M after” before deciding. The fixed file costs 19 € (excl. VAT); the check is free. We never call a file “accessible” or “compliant”.

Other rules in clause 7.21.6

• 7.21.6-1 For all non-symbolic TrueType fonts used for rendering, the embedded TrueType font program shall contain one or several
• 7.21.6-2 All non-symbolic TrueType fonts shall have either MacRomanEncoding or WinAnsiEncoding as the value for the Encoding key
• 7.21.6-4 The 'cmap' table in the embedded font program for a symbolic TrueType font shall contain either exactly one encoding or

Rule text (description and error message): veraPDF validation profile PDF/UA-1 © veraPDF Consortium, licensed under CC BY 4.0. This site is not affiliated with the veraPDF Consortium, the PDF Association, ISO or Adobe. Adobe and Acrobat are trademarks of Adobe; the Acrobat checker item is named only to help you match the two reports.