Font Diagnosis and Tracing

12-8 Publishing Reports to the Web with Oracle Reports Services 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.4.2 Deploying Your Report

Deploying a Report in 11g that uses the New Font Model 1. Ensure that the REPORTS_ENHANCED_FONTHANDLING environment variable is set to yes. The default value is yes.

2. Copy all the TTF and TTC files, which are used in the report, to the REPORTS_

FONT_DIRECTORY. The default font directory is ORACLE_ INSTANCEreportsfonts.

3. Remove any unnecessary aliasing from the uifont.ali file. For example, Arial is

aliased to Helvetica, by default. If your report uses the Arial font, you must remove the aliasing from the uifont.ali file.

4. Run the Report.

Deploying Reports 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 when AFM font files are not available:

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. 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