Defining custom fonts and TrueType fonts
Custom fonts
When you view an AFP file in RICOH ProcessDirector, the file viewer converts the file to be displayed. In the process, it looks for the AFP fonts that the file uses in these places:
- Inline with the job
- In the directories specified by the AFP resource path job property, if the AFP Support feature is installed
- In
/aiw/aiw1/resources
(Linux) orC:\aiw\aiw1\resources
(Windows) - In
/usr/lpp/psf/reslib
(Linux) orC:\Program Files (x86)\Ricoh\PSF\reslib
(Windows)
cpdef.fnt
and csdef.fnt
). When those files are installed, the font listed in the DEFAULT section is Times New Roman, 8-point and the code page is EBCDIC 500, although they
can be changed. The content of the AFP file is not changed, but the displayed version
might not look the same as the final printed version. If the code page or the font
is not defined in the configuration files and it is not an EBCDIC code page, the file
viewer displays unreadable text.
If you do not need to see the exact fonts that are referenced in the document, you do not have to change your font configuration files. However, if most or all of your jobs are going to cause these types of errors to be displayed, you might want to define at least some of your custom fonts, character sets, and code pages to the viewer, so that you can reduce the number of error messages that appear.
The font configuration files shipped with RICOH ProcessDirector contain mapping information for the IBM Core Interchange Latin fonts, the Compatibility
and Coordinated fonts, and the IBM Sonoran and Data1 fonts so you only need to update
the files if your custom fonts are not one of those font sets. If you have generated
font configuration files for the RICOH AFP to PDF transform of InfoPrint Manager, AFP Workbench for Windows, or the AFP Windows Viewer plug-in, you can just copy
those files into the /opt/infoprint/ippd/afpviewer/font
(Linux) or C:\Program Files\Ricoh\ProcessDirector\afpviewer\font
(Windows) directory.
- Note:
- Although it is not described here, the viewer component of RICOH ProcessDirector does use an
ALIAS.FNT
file. TheALIAS.FNT
file that RICOH ProcessDirector uses is in the same format as theALIAS.FNT
that InfoPrint Manager uses. As a result, if you have edited theALIAS.FNT
file that you use with InfoPrint Manager, you can copy it into the/opt/infoprint/ippd/afpviewer/font
(Linux) orC:\Program Files\Ricoh\ProcessDirector\afpviewer\font
(Windows) directory and use it with RICOH ProcessDirector. This file is different from theALIAS.FNT
file used by the AFP Workbench and AFP Windows Viewer plug-in.
Font mapping information is recorded in several files. You might have to edit more than one of them.
TrueType and OpenType fonts
AFP files can also contain references to TrueType and OpenType fonts. When the viewer
finds a reference to a TrueType or OpenType font, it searches the TrueType font configuration
file (ttdef.fnt
) for a mapping to a Type 0 or Type 1 font. If a mapping is found, the Type 0 or Type
1 font is used.
If no mapping is found, the viewer searches for the TrueType or OpenType font in these places:
- The AFP file to see if the TrueType font is included inline
- The path set by the TT_Font_Path entry in the viewer configuration file
/opt/infoprint/ippd/afpviewer/font/truetype
(Linux) orC:\Program Files\Ricoh\ProcessDirector\afpviewer\font\truetype
(Windows)- The AFP resource path directory for the job
- Note:
- Because double-byte character set (DBCS) TrueType fonts are very large, you should consider mapping them to one of the DBCS fonts that the AFP viewer processes efficiently: JpnSys1 (KozGoPro-Medium) or JpnSys2 (KozMinPro-Regular).