Embedded fonts: preserve text all the way to the RIP

Why a missing font remains a print risk

When a font is not embedded, the output system may search for a local copy or substitute another font. Letter shapes, spacing, hyphenation and line breaks can then differ from the approved document.

A correct preview does not prove the RIP has the same resource. The report must inspect what the PDF carries instead of relying on fonts installed on the operator’s workstation.

Full font or subset

Full embedding includes all permitted glyphs. A subset carries only characters required by the document and normally uses a distinct prefix in its internal name.

For fixed output, a coherent subset can preserve appearance while limiting file size. Preflight must still confirm that every used character has a glyph and that encoding remains usable.

Respect embedding permissions

Font files can include permissions chosen by the foundry. A licence may allow preview and print, allow editing, or prohibit embedding. Software must not bypass these restrictions.

If embedding is unavailable, re-export from the source with a permitted font, obtain the required licence, or use an approved text-to-outline process that preserves the intended appearance and any required accessibility.

Useful information in a font check

The check should list font name, type, embedding status and, where possible, pages using it. Partially embedded fonts or unusual encodings deserve an explicit conclusion rather than one global count.

• Fully embedded font or embedded subset.
• Referenced font missing from the file.
• Missing glyphs or uninterpretable encoding.
• Detectable embedding restrictions.
• Affected pages and objects for faster source correction.

Automatic correction or REVIEW

A font can be embedded reliably only when the exact resource is available, its rights permit the operation and the output can be validated again. Those conditions are rarely all true for a customer PDF received without source fonts.

Conservative behaviour is to detect and locate the issue, then request a new export. A substitution that merely looks acceptable is not enough to declare the file READY.