EN16931 / XRechnung / Peppol BIS 3 Validator

PDF/UA-1 rule reference › clause 7.21.7

PDF/UA-1 rule 7.21.7-1: The glyph can not be mapped to Unicode

Not fixed automatically font

What veraPDF reports

The glyph can not be mapped to Unicode

veraPDF rule 7.21.7-1 = ISO 14289-1:2014 clause 7.21.7, test 1, checked on PDF object Glyph.

In Adobe Acrobat’s Accessibility Checker the closest item is “Character encoding”.

What the requirement says

The Font dictionary of all fonts shall define the map of all used character codes to Unicode values, either via a ToUnicode entry, or other mechanisms as defined in ISO 14289-1, 7.21.7

Can it be fixed automatically?

Not fixed automatically. This failure needs the authoring tool or manual remediation; the automatic fix does not change it.

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.7

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.