Specifying font substitution through initialization files

Sometimes jobs request fonts that are neither included inline with the job nor resident on the printer. If InfoPrint Manager cannot find the fonts that the job requires, the job might fail. To avoid job failure because of missing fonts, you can issue a PostScript command that substitutes a Courier font to make sure that the job prints.

To do this task, use this procedure:

  1. From a command line, access the UserInit file that is located in the /var/psf/ps2afp2 directory on an InfoPrint Manager AIX or InfoPrint Manager for Linux server. If you are using a configuration file and daemon other than the default 3160d.cfg postscript daemon configuration file, the you will need to determine which daemon is being used and change the initialization file for that daemon.
  2. Using your editor of choice, edit the file.
  3. Add this to the UserInit file to make sure that missing fonts are replaced by Courier fonts to allow the job to print : 
    %!
turnFontSubstitutionOn
    Note: If you want to make sure that fonts not inline with the job or resident on your printer do not print, type this change in the UserInit file: 
    %!
turnFontSubstitutionOff
  4. Save and close the file.

Note: For your convenience, InfoPrint provides samples (UserInit file, font.subs.on, and font.subs.off) in the /usr/lpp/psf/ps2afp directory on an InfoPrint Manager AIX or InfoPrint Manager for Linux server.

You can use the desktop Text Editor to rename the font.subs.on or font.subs.off files and use this UserInit file at your installation.

Parent topic: Fonts for printing transformed PostScript and PDF data