Learn in this article,
- how to embed missing fonts
- how to convert fonts to outlines, as well as
- where these Fixups can be accessed in the Workflow and
- which additional information for fonts is substantial for the processing of print data.
1. Introduction
It is theoretically possible to transfer the description of used fonts (font programs) to a PDF when fonts in the source applications can be accessed at the time of the PDF creation. If it is not possible to access the fonts used at the time of PDF creation, the used glyphs can be embedded. However, it is not possible to embed the descriptive outlines of the glyphs. In the first case we speak of embedded fonts and in the second case of missing fonts.
2. General
The below listed Fixups can be found in the footer of the Font [1] settings area of the Print Data tab of an Article or Print Item. In addition, the Fixups can be found in the Data Preparation tab.
With these Fixups, problems in the environment of fonts can be solved while processing Print Data and errors in the RIP can be prevented. Further Fixups are not available in the font environment of the Workflow. However, it should be noted that additional Fixups are automatically applied in the background during the upload process.
Figure 1: The Fonts setting area of the Print Data tab of an Article or Print Item
3. Fixups for Fonts
The two most important Fixups - Convert Fonts to Outlines [3] and Embed missing Fonts [2] are available in the environment of processing fonts in the Workflow. Additional Fixups in this environment - e.g. making font names unique, adapting font encodings and correcting incorrect Unicode mappings - are already applied automatically in the background when uploading Print Data.
3.1. Embed missing Fonts
The Fixup Embed missing Fonts [2] (Figure 1)aims to embed missing fonts so that a complete processing of the outline description for glyphs can be ensured. Only if fonts are embedded error-free output in print, editing of texts, as well as a conversion of fonts into outlines is possible.
Fonts can only be embedded if they are directly accessible in the Workflow. All typical font directories of the Windows operating system are accessible . Furthermore, selected directories of the Workflow can be used to make fonts available in the Workflow.
Figure 2: The Embed missing Fonts dialog
Find out more about the functionality of this Fixup with a corresponding sample file and description here.
3.2. Convert Fonts to Outlines
The aim of the Fixup Convert Fonts to Outlines [2] (Figure 1) is to convert embedded fonts into outlines. During the conversion, the outline description of the glyphs in the font program is used to resolve the individual glyphs in the PDF as vector graphics. However, the conversion to outlines can only take place if the corresponding outline description is available, i.e. the font is embedded.
By converting glyphs into outlines, some of the storage space for the PDF can be reduced. On the other hand, output reliability in printing can be significantly improved, as no font conflicts can occur in the RIP. However, if extensive text documents are converted into outlines, this can lead to an increase in the memory requirements for the PDF. This can result in poorer output quality of texts with low-resolution - below 300 dpi - printing systems, and can also prevent texts from being changed before printing. Whether fonts should be converted to outlines or not therefore always depends on the intended use.
Figure 3: The Convert Fonts to Outlines dialog
Find out more about the functionality of this Fixup with a corresponding sample file and description here.
Article update: Workflow 1.17.1 - 03/2024