Publishing Reports to the Web - Downloads - Oracle

.....TR8MSWIN1254="Courier New"
Troubleshooting Font Issues
You can download a copy of the Andale Duospace WT (fixed-width) font from
Metalink, (http://metalink.oracle.com). The ARU number is 2638552.
Limitations
On Windows:
■ For Unicode, Oracle Reports relies on the Windows operating system for the font
and input method for different languages. To enter and display text in a particular
language, you must be running a version of Windows that supports that language.
Font support is limited, but not restricted, to the Windows NT operating system
font support.
■ In JDK, a bug causes the bold Korean font to appear incorrectly. OracleAS Reports
Services uses the JRE and therefore all bold Korean strings in graphs within
reports show up incorrectly.
■ Windows NT 4.0 and later versions, provides True Type Big Fonts. These fonts
contain all the characters necessary to display or print multilingual text. If you try
to type, display, or print multilingual text and see unexpected characters, you are
probably not using a big font. Big fonts provided by Microsoft under NT 4.0 and
later, are as follows: Arial, Courier New, Lucida Console, and Lucida Sans
Unicode. Arial Unicode MS, which is a true big font, is available from Microsoft
site for download.
■ Wingdings fonts may not appear when NLS_LANG is UTF8.
The only Wingdings fonts available when using UTF8 are the characters between
ASC 32 and 127. ASC 252 would display a blank because it is not supported by
UTF8.
Any of the following font sets would provide a reasonable work around.
■ Webdings - chr(97)
■ Wingdings2 - chr(80)
■ Wingdings2 - chr(87)
On UNIX:
■ AFM support is only for single byte PostScript file generation except for the
Japanese encoding. The encoding schemes supported for the AFM files are
AdobeStandardEncoding, ExtJIS12-88-CFEncoding, FontSpecific, HRoman,
ISOLatinHebrew, JIS12-88-CFEncoding, and JIS12e-88-CFEncoding.
AFM version that is supported is 2.0
■ X11 does not support the underline font attribute. Output to file should work
according to steps given below.
■ In JDK, a bug causes the bold Korean font to appear incorrectly. OracleAS Reports
Services uses the JRE and therefore all bold Korean strings in graphs within
reports show up incorrectly.
■ PostScript printing will not load the fonts to the printer. So for the desired fonts to
appear in the printed output, it is necessary that those fonts should be installed on
the printer.
■ For PCL output, only TFM font formats are supported.
Managing Fonts in Oracle Reports 4-19