Using non-Latin code pages with Outline fonts

The afp2pdf transform supports non-Latin codepages for AFP Outline fonts.

These non-Latin code pages are supported:

  • 259
  • 290
  • 420
  • 423
  • 424
  • 833
  • 836
  • 838
  • 870
  • 875
  • 880
  • 892
  • 893
  • 904
  • 1025
  • 1026
  • 1027
  • 1097
  • 1112
  • 1122
  • 1130
  • 1132
  • 1153
  • 1154
  • 1155
  • 1156
  • 1157
  • 1158
  • 1160
  • 1164

When an AFP document contains text written in one of the supported non-Latin code pages, the afp2pdf transform uses a corresponding AFP Outline Font. Each code page has a corresponding AFP Outline font. The location of the AFP Outline fonts is specified in the configuration file using the Foca_Font_Path option. To display the text written with the non-Latin code-pages within the PDF, the afp2pdf transform extracts the PFB file from the AFP Outline Fonts and creates a PFM file. The resulting files are embedded within the PDF stream. When a non-Latin code page does not find the corresponding AFP Outline Font, the afp2pdf transform converts the text to a default code-page. This default code page is set in the cpdef.fnt file. The default code page is one of the base-14 Standard PDF fonts.

To accommodate the non-Latin code pages, these options have been added to the afp2pdf.cfg file. The configuration file (afp2pdf.cfg) has these new options:

For AIX or Linux
Foca_Font_Path = /usr/lpp/psf/fontlib specifies the path for the AFP Outline fonts.
For Windows
Foca_Font_Path = \install_path\fontlib specified the path for the AFP Outline fonts.
    Note:
  • If the configuration file does not contain the Foca_Font_Path entry, the afp2pdf transform searches within /usr/lpp/psf/fontlib for AIX or Linux, and \install_path\fontlib for Windows.