Editing the Type 1 and Type 0 font map

If the TrueType font definition file maps TrueType or OpenType fonts to any non-standard Type 1 or Type 0 fonts, you must supply the Printer Font Metrics (.pfm) and Printer Font Binary (.pfb) files for these fonts and edit the Type 1 and Type 0 font map.

The fontmap.lst file has two sections. The font directory section lists the directories where non-standard Type 1 and Type 0 fonts reside. The font name section maps the PostScript name of each non-standard font to its file names.

In the font directory section, the lines use this syntax:

$Font_Directories (pfm_directory) (pfb_directory)
$Abs_Path_Prefix (absolute_path_prefix)

pfm_directory: The full path name of a directory that contains .pfm files, not including the final slash (/ or \). You can specify only one value for pfm_directory on each $Font_Directories line, but you can specify multiple lines.
pfb_directory: The full path name of a directory that contains .pfb files, not including the final slash (/ or \). You can specify only one value for pfb_directory on each $Font_Directories line, but you can specify multiple lines.
absolute_path_prefix: A string at the beginning of a font reference that indicates that the reference is an absolute path. You can specify up to 10 values for absolute_path_prefix on a single $Abs_Path_Prefix line. Each value can be 1 to 7 characters (bytes). Enclose each value in parentheses.

For example, the font directory section might contain these entries:

For Linux:
$Font_Directories (/opt/infoprint/ippd/ProcessDirector/afpviewer/font/pfm) (/opt/infoprint/ippd/ProcessDirector/afpviewer/font/pfb)
$Font_Directories (usr/local/lib/ghostscript/fonts) (usr/local/lib/ghostscript/fonts)
$Font_Directories (.) (.)
$Abs_Path_Prefix (/) 

For Windows:
$Font_Directories (C:\Program Files\Ricoh\ProcessDirector\afpviewer\font\pfm) (C:\Program Files\Ricoh\ProcessDirector\afpviewer\font\pfb)
$Font_Directories (usr\local\lib\ghostscript\fonts) (usr\local\lib\ghostscript\fonts)
$Font_Directories (.) (.)
$Abs_Path_Prefix (\)

In the font name section, the lines use this syntax:

font_name (pfm_file) (pfb_file)

font_name: The PostScript name of a Type 0 or Type 1 font.
pfm_file: The file name of the .pfm file for that font, including the file extension.
pfb_file: The file name of the .pfb file for that font, including the file extension.

For example, the font name section might contain these entries:

Garamond-Light       (GAL_____.PFM) (GAL_____.PFB)
Garamond-Bold        (GAB_____.PFM) (GAB_____.PFB)
Garamond-LightItalic (GALI____.PFM) (GALI____.PFB)
Garamond-BoldItalic  (GABI____.PFM) (GABI____.PFB)

To edit the Type 1 and Type 0 font map:

On Linux, log in to the primary computer using a user ID that is a member of the RICOH ProcessDirector group (aiwgrp1 is the default).
Then make sure that the RICOH ProcessDirector group has read permission for the .pfm and .pfb files that you want to use.
Navigate to /opt/infoprint/ippd/ProcessDirector/afpviewer/font (Linux) or C:\Program Files\Ricoh\ProcessDirector\afpviewer\font (Windows) and find the file fontmap.lst.
Copy the file fontmap.lst and save it as a backup.
For example, you can save the copy as fontmap.lst.bak.
Open fontmap.lst in a file editor.
Insert new lines for the Type 1 and Type 0 fonts in both sections, using the syntax above.
- The font directory section must be before the font name section.
- The $Abs_Path_Prefix line must be the last one in the font directory section. Add your $Font_Directories lines above it.
- A pound sign (#) or a percent sign (%) in the first column causes that line to be treated as a comment.
- All values are case-sensitive.
- All parameters are positional.
- Blanks are allowed between parameters.
Save and close the file.

RICOH ProcessDirector™ for Windows

Editing the Type 1 and Type 0 font map

Other topics in this section:

Related information: