CID Fonts Font Types

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: Managing Fonts in Oracle Reports 9-21 The test results below are based on a Lexmark Optra printer. The fonts and their numbers as well as the control commands are examples and may vary with other printers. Font information The Lexmark has a small menu with the option of printing all available fonts PCL Emulation Fonts. This includes both resident fonts defaults and Flash fonts installed on the printer separately In these examples, there are many more fonts and each font has its own code. OCRB for example has code 4206. This number is important later on. Creating Output When having problems getting the correct font, simplify the report and thereby the output. This can be done by creating a straightforward report using select sysdate from dual as the query and limiting the number of fonts. This will avoid long runs and create much smaller output files. Reading the Output File The resulting PCL-file is a binary file but is reasonably readable in the VI editor. The first small part and the end part is binary, but the middle part is readable and contains data that can be interpreted. Verifying the Output File The only interesting information is in the readable, middle part of the file. Find the text this is the text displayed in the reports output and check out the part preceding the text. It looks like this: ....;SD1,14,2,0,3,10.34,5,0,6,0,7,4099;LB here is your text In the preceding example, the font is selected with code 4099. For the Lexmark printer, this is selecting Courier. Table 9–6 Sample Font Information Font Name Style Weight Example Output R0 Courier ... ESCsymsetESCs0ppitchh0s0b4099T... R39 Courier Bold 3 ... ESCsymsetESCs0ppitchh0s3b4099T... R40 Courier Italic 1 ... ESCsymsetESCs0ppitchh1s0b4099T... R55 Century Schoolbook Roman ... ESCsymsetESCs1ppointv0s0b24703T ... Table 9–7 Sample Flash Font Information Font Name Symbol Set Style Weight Example Output F2 OCR-A 0O ... ESC0OESCs0ppitchh0s0b4200T ... F3 OCR-B 1O 3 ... ESC1OESCs0ppitchh0s0b4206T ...