The PPD file that you modified should be picked up. If it is not picked up it is

Font Model and Cross-Platform Deployment 12-13 ■ Deploying Your Report in Pre-11g Version That Uses Motif Tool Kit Mechanism ■ Frequently Asked Questions

12.5.1 Designing Your Report

To prepare your report before you deploy it on a UNIX platform: 1. Create a new report. 2. Use only those fonts in your report that: ■ Are available on UNIX. All font files that are available on Windows TTF files may not be available on UNIX AFM or TFM files. If you have the correct AFM or TFM font file available on the UNIX platform, you can continue to use it AFM for PostScript and TFM for PCL. ■ Can scale well. For example, MS Sans Serif does not scale well to a different size, whereas Tahoma does. The reason is that the MS Sans Serif font is a raster font that does not scale well to any size and usually has rounding issues. On the other hand, Tahoma font is a TrueType font that is very similar in visual appearance to the MS Sans Serif font. Additionally, Tahoma is a vector font that can be scaled to any size and rotated to any angle.

12.5.2 Deploying Your Report in Pre-11g Version That Uses Motif Tool Kit Mechanism

For fonts with AFM files not readily available on UNIX, or if you encounter any font issues in the report output such as text misalignment, you can convert and generate an AFM file from the Windows TTF file using freely available third party utilities, such as ttf2pt1. Do not attempt to convert to a TFM file, as this may not produce reliable results. To deploy your report on a UNIX platform using PDF font subsetting: 1. Locate the TTF files corresponding to the fonts used in your report. Convert these TTF files to AFM to ensure that you will have the AFM files for the fonts used in your report. Use a True Type to Type 1 font converter utility to convert the TTF files to AFM files. For example, ttf2pt1. 2. Post-conversion, remove the .afm extension in the AFM file name. For example: Note: AFM support is extended only to single-byte PostScript file generation, with the exception of Japanese encoding. The encoding schemes supported for the AFM files are: AdobeStandardEncoding ExtJIS12-88-CFEncoding FontSpecific HRoman ISOLatinHebrew JIS12-88-CFEncoding JIS12e-88-CFEncoding