In this article, you will learn
- which Fixups are available within a Check-in Preflight and Fixup Template for Fonts and Text, and
- for which Use Cases these Fixups are suited for.
1. Introduction
When print files are uploaded to the Workflow, the documents are checked by using Check-in Preflight and Fixup Templates, and are partially automatically corrected and brought into a normalized state. Normalizing print data is therefore a key step in prepress, as it saves time, reduces sources of errors, and automates essential tasks.
Not all Fixups are available within a Check-in Preflight and Fixup Template
Within the Workflow, a clear distinction is made between normalizing print data and preparing print data for printing. The normalization step brings print data to a consistent standard for data preparation. The corresponding data preparation for production takes place at a later stage through the targeted application of individual Fixups or Fixup Chains.
2. Available Fixups for Font and Text
To take full advantage of Check-in Preflight and Fixup Templates, these templates must first be created. A template essentially consists of Checks and Fixups. Currently, more than 40 different Fixups are available in the Workflow. To maintain clarity, the individual Fixups are organized into thematic categories.
This article provides a detailed overview of all available Fixups that can be used to correct, embed, and adjust font and text elements.
2.1. Convert font names to UTF-8
Category: Font
Description: This Fixup renames font names that are not encoded in UTF-8 to UTF-8-encoded font names.
Use Case: Some PDF-based ISO standards require all font names to be encoded in UTF-8. This Fixup should be applied to produce print data compliant with these ISO standards.
Figure 1: The activated Fixup Convert font names to UTF-8
2.2. Embed missing fonts
Category: Font
Description: This Fixup attempts to identify missing fonts in the print file, locate them on the system, and embed them automatically. It searches both the system's default font directory on where the Workflow is installed and an additional specified directory path (for example, D:\PMS_DATA\ZuniComm\FONT_STORE).
Use Case: This Fixup is applied during the chek-in of print files where fonts were not embedded when the print file was created. Such problems frequently occur with files from Office applications, where standard fonts such as Calibri, Arial, Times, etc. are often not embedded when exporting to PDF. To ensure that the Workflow does not proceed with incomplete print data, this Fixup should be included in every Check-in Preflight and Fixup Template. The Fixup interrupts the process by displaying an error message, thereby ensuring a reliable database for further processing.
Figure 2: The activated Fixup Embed missing fonts
Adjusting the path
Please ensure that the path specified in this Fixup is adjusted if the Workflow is installed on a different hard disk on the workstation.
2.3. Remove additional encoding for TrueType fonts
Category: Font
Description: This Fixup attempts to remove all but one encoding from the «CMap» table of an embedded symbolic TrueType font, without altering the visual appearance. Some PDF-based ISO standards require that no more than one encoding be used. This Fixup is also compatible with other PDF/X versions.
Use Case: This Fixup should be applied when generating print data that needs to comply with the required ISO standards.
Figure 3: The activated Fixup Remove additional encoding for TrueType fonts
Article update: Workflow 1.20.1 – 05/2025