Enhanced BIDI Reshaping Bidirectional Support

Implementing Globalization and Bidirectional Support 23-15 Oracle Reports looks for this file in the directory ORACLE_ INSTANCEconfigFRComponentfrcommonguicommontkadminlanguag, where, language is derived from the language setting in NLS_LANG. If the file does not exist, then Oracle Reports looks for the default version in ORACLE_ INSTANCEconfigFRComponentfrcommonguicommontkadmin. This version is configured for WEISO8859P1, the Western European character set. If your NLS_LANG or NLS_CHARACTERSET specifies a character set that is not normally used for the language you have set in NLS_LANG, then Oracle Reports generates an error. For example, if you have set NLS_LANG=AMERICAN_AMERICA.JA16EUC, then Oracle Reports locates Tk2Motif.rgb in the directory ORACLE_ INSTANCEconfigFRComponentfrcommonguicommontkadmin. The language setting in NLS_LANG is AMERICAN, and there is no language subdirectory associated with AMERICAN, so Oracle Reports uses the default file. Since this version is designed for WE8ISO8859P1, and your NLS_LANG character set is JA16EUC, Oracle Reports generates the error REP-3000. To work around this problem, set the value of the environment variable TK_UNKNOWN to the location of your character set-specific Tk2Motif.rgb file. For example, if NLS_LANG=AMERICAN_AMERICA.JA16EUC, then set TK_ UNKNOWN=ORACLE_ INSTANCEconfigFRComponentfrcommonguicommontkadminJA. Even though your language is set to AMERICAN, Oracle Reports will use the Tk2Motif.rgb file in the JA language subdirectory. Repairing Garbled Fonts When Using the WE8ISO8859P15 Character Set You may see garbled output when you run a multibyte report on UNIX with we8iso8859p15 character set. To work around this issue, you must do the following: 1. Make an entry for the fonts used in your default printers .ppd file. This file is located in the following directory: ORACLE_HOMEguicommontkadmin 2. Set the encoding scheme in the fonts AFM file to FontSpecific if it is AdobeStandardEncoding. Thus, the following entry in the AFM file: EncodingScheme AdobeStandardEncoding must change to: EncodingScheme FontSpecific Opening or Running an Encoded JSP Report If your JSP reports character encoding for example, EUC-JP differs from the character set portion of the NLS_LANG environment variable for example, JA16SJIS, then you will get the following errors: ■ when running the JSP file: Note: The entries are for the fonts that appears garbled in the report output.