Mapping AFP fonts

The afp2pdf transform needs to map the AFP fonts your document was created with to fonts that can be used in PDF documents.

For the afp2pdf transform to map the best matching fonts to display your AFP document, the transform needs to know certain characteristics about the fonts that were used to create your document. Mapping AFP fonts is done with the font definition files installed as part of the afp2pdf transform. These files are loaded into the FONT subdirectory under /opt/infoprint/itm/xforms/afp2pdf/ for Linux and under TF_install_path\itm\xforms\afp2pdf\ for Windows. FONT subdirectory with an AFM subdirectory and a Type1 subdirectory. You can edit them using any text editor. The shipped version of the font definition files maps the IBM Core Interchange (Latin only), compatibility, coordinated, and Data1 fonts for you. If your document uses an AFP font that is not listed in the font definition files, you need to add it. If you have generated modified font definition files for viewing AFP files for the AFP Workbench or for the AFP plug-in, some of the same files can be reused for the afp2pdf transform. The icoded.fnt, coded.fnt, csdef.fnt, cpdef.fnt, and ibm-CPID.cnv, where CPID is the code page identification number, files can be copied and used for the transform. Do not try to reuse the ALIAS.fnt file.

In this section:

  1. When you need to map fonts
    If you are using fonts that are not defined for the afp2pdf transform, if you have modified the IBM AFP fonts, or if you have created your own AFP fonts, you need to define those fonts in the font definition files:
  2. The afp2pdf transform files supplied for mapping fonts
    The next table lists the afp2pdf transform font support files and the subdirectories in which they are installed.
  3. Mapping fonts with non-Latin encodings
    When you use external fonts that contain glyphs that are not part of the Latin encoding, use this procedure to embed them in the PDF file.
Parent topic: Transform AFP data to PDF