TrueType Fonts Font Types

Managing Fonts in Oracle Reports 9-19 3. If you have a valid printer, configure the printer in the uiprint.txt file and change the DefaultResolution to 600. 4. Run the report after placing the fonts in the font folder.

9.7 Running a Unicode Report using TTFTTC Fonts

Oracle Reports 11g Release 1 11.1.1 uses the new font mechanism to run a Unicode report on UNIX using the TTF TTC fonts, generating report output that in most cases looks identical on both platforms. Run a sample Unicode report on Windows for example, Unicode.rdf in the sample reports directory:

1. In Oracle Enterprise Manager, select Reports Administration FormsReports

Common Configuration to display the Forms Reports Common Component Configuration Page. ■ Add the following entry under the [PDF:Subsetting] section: Arial Unicode MS=ARIALUNI.TTF ■ Ensure there is no aliasing defined for Arial in the Global section. If there is, comment it out: Arial=Helvetica 2. Add the font ARIALUNI.TTF to REPORTS_PATH. 3. Set NLS_LANG in the Windows registry to AMERICAN_AMERICA.UTF8. 4. Open the sample report in Reports Builder.

5. Select File Generate to File PDF if running the sample Unicode.rdf,

choose P_LANG_ID=JA. 6. Save the report output. Run the same Unicode report on UNIX : 1. Check whether the Unicode font used by the report is already available on the UNIX server machine in ORACLE_INSTANCEreportsfonts and in the REPORTS_PATH for example, ARIALUNI.TTF. If it is not available, copy it from the Windows machine to ORACLE_INSTANCEreportsfonts. 2. Set NLS_LANG in reports.sh to AMERICAN_AMERICA.UTF8. 3. Run the report using the following command line: http:host:portreport=report_ name.rdfdestype=cachedesformat=pdfuserid=userpassworddb For example: http:host:portreport=Unicode.rdfdestype=cachedesformat=pdfP_LANG_ ID=JAuserid=oeoemydb Compare the output on UNIX with that on Windows to confirm that they are identical.

9.8 Diagnosing Font Issues

To diagnose font usage and issues, you can view the log files in either of the following ways: 9-20 Publishing Reports to the Web with Oracle Reports Services ■ Using the Command Line ■ Using Oracle Enterprise Manager

9.8.1 Using the Command Line

To view the log files using the command line: ■ Open the diagnostics log file: ORACLE_INSTANCEdiagnosticslogsReportsServerComponent server_namerwEng-id_diagnostics.log ■ Notice that the font used for each object in the report is logged without any ambiguity. If a TTF font file was not found, it is logged and noted that the pre-11g mechanism was used for finding the appropriate font, which is also logged.

9.8.2 Using Oracle Enterprise Manager

Refer to Section 7.11.1, Viewing and Searching Log Files in Chapter 7, Administering Oracle Reports Services Using Oracle Enterprise Manager

9.9 Troubleshooting Font Issues

To help resolve font issues that may occur in your applications, this section provides the following troubleshooting information: ■ Checking Whether the Desired Font Is Used in a PostScript File ■ Creating Output ■ Reading the Output File ■ Verifying the Output File ■ Correcting Printed Font ■ Checking Environment Variables ■ Repairing Fonts Not Appearing Correctly in Web Source View ■ Understanding Limitations ■ Resolving Common Problems Checking Whether the Desired Font Is Used in a PostScript File PostScript files have a list of fonts, which is created after reading the PPD file. If you examine the PostScript file, you can check the fonts by looking for the following tags: ■ DocumentNeededResource has the list of fonts referenced in the PPD file. ■ DocumentSuppliedResource has the list of fonts for which the PostScript driver was able to find the AFM file. ■ Page paragraph before the fields IncludeResource:font has the font name which will be used for the field. For PCL output files, you can check whether a particular font was used or not. Depending on this information the font settings in Oracle Reports or the printer can be modified. Example: