C Configuring Oracle Database Companion CD Globalization Support

This appendix describes the following Globalization Support topics:

Installing and Using Oracle Components in Different Languages
Configuring Locale and Character Sets by Using the NLS_LANG Environment Variable

C.1 Installing and Using Oracle Components in Different Languages

This section describes the following procedures:

Installing Oracle HTML DB in Different Languages
Installing Oracle Workflow in Different Languages
Running Oracle Universal Installer in Different Languages
Using Oracle Components in Different Languages

C.1.1 Installing Oracle HTML DB in Different Languages

The Oracle HTML DB interface is translated into German, Spanish, French, Italian, Japanese, Korean, Brazilian Portuguese, Simplified Chinese, and Traditional Chinese. A single instance of Oracle HTML DB can be installed with one or more of these translated versions. At run time, each user's Web browser language settings determine the specific language version.

The translated version of Oracle HTML DB should be installed in a database that has a character set that can support the specific language.

Caution:

If you attempt to install a translated version of Oracle HTML DB in a database that does not support the character encoding of the language, then the installation may fail or the translated Oracle HTML DB instance may appear corrupted when run.

The database character set AL32UTF8 supports all the translated versions of Oracle HTML DB.

You can manually install translated versions of Oracle HTML DB by using SQL*Plus. The installation files are encoded in UTF8.

Caution:

AL32UTF8 is the Oracle Database character set that is appropriate for XMLType data. It is equivalent to the IANA registered standard UTF-8 encoding, which supports all valid XML characters.

Do not confuse the Oracle Database database character set UTF8 (no hyphen) with the database character set AL32UTF8 or with character encoding UTF-8. Database character set UTF8 has been superseded by AL32UTF8. Do not use UTF8 for XML data. UTF8 supports only Unicode version 3.1 and earlier; it does not support all valid XML characters. AL32UTF8 has no such limitation.

Using database character set UTF8 for XML data could potentially cause a fatal error or affect security negatively. If a character that is not supported by the database character set appears in an input-document element name, a replacement character (usually, the question mark (?)) is substituted for it. This will terminate parsing and raise an exception.

Note:

Regardless of the target database character set, to install a translated version of Oracle HTML DB, you must set the character set value of the NLS_LANG environment variable to AL32UTF8 before starting SQL*Plus.

The following examples illustrates valid NLS_LANG settings for loading Oracle HTML DB translations:

American_America.AL32UTF8
Japanese_Japan.AL32UTF8

To install a translated version of Oracle HTML DB:

Set the NLS_LANG environment variable. The character set must be AL32UTF8. For example:

Bourne, or Korn shell:
```
NLS_LANG=American_America.AL32UTF8
export NLS_LANG
```
C shell:
```
setenv NLS_LANG American_America.AL32UTF8
```
Start SQL*Plus, and connect to the target database as SYS.

Run the following statement:

ALTER SESSION SET CURRENT_SCHEMA = FLOWS_010600;

Run the appropriate language-specific script. For example:
```
@load_de.sql
```
The installation scripts are located in subdirectories identified by a language code in the unzipped distribution /htmldb/builder. For example, the German version is located in /htmldb/builder/de and the Japanese version is located in /htmldb/builder/ja. In each of these directories, there is a language loading script identified by the language code. For example, load_de.sql or load_ja.sql.

C.1.2 Installing Oracle Workflow in Different Languages

Use the Add Language option in Oracle Workflow Configuration Assistant to install Oracle Workflow in a different language.

C.1.3 Running Oracle Universal Installer in Different Languages

Oracle Universal Installer runs by default in the selected language of your operating system. You can also run Oracle Universal Installer in one of the following languages:

Brazilian Portuguese
German
Japanese
Simplified Chinese
Traditional Chinese
French
Italian
Korean
Spanish

Note:

If the language set for the operating system is not supported by Oracle Universal Installer, then Oracle Universal Installer, by default, will run in the English language.

To run Oracle Universal Installer in another available language, change the language in which your operating system is running before you run Oracle Universal Installer.

C.1.4 Using Oracle Components in Different Languages

You can specify the language in which you want to use Oracle components (such as Oracle Net Configuration Assistant and Oracle Database Configuration Assistant). Note that this does not change the language in which Oracle Universal Installer is run. For the Oracle component to run in the selected language, it must be the same as the language set for your operating system. You can change your operating system language in the Regional Settings window from the Control Panel.

To use components in different languages:

Start Oracle Universal Installer.
On the Select Installation Type screen, click Product Languages.
On the Language Selection screen, select the language in which you want to use Oracle components from the Available Languages field.
Use the > arrow to move the selected language to the Selected Languages field, and then click OK.
Select the products you want, and then click Next.

After installation is complete, the dialog box text, messages, and online Help for the installed components are displayed in the language you select.

C.2 Configuring Locale and Character Sets by Using the NLS_LANG Environment Variable

Oracle provides Globalization Support that enables users to interact with a database in their preferred locale and character set settings. Setting the NLS_LANG environment variable specifies locale behavior for Oracle software. It sets the language and territory used by the client application and the database. It also sets the character set for entering and displaying data by a client program, such as SQL*Plus.

The NLS_LANG environment variable uses the following format:

NLS_LANG=language_territory.characterset

In this format:

language_territory specifies the language used for displaying Oracle messages, sorting, day names, and month names
territory specifies the conventions for default date, monetary and numeric formats
characterset specifies the encoding used by the client application

In most cases, this is the Oracle character set that corresponds to the character set of the user terminal or the operating system.

The NLS_LANG environment variable is set as a local environment variable for the shell on all UNIX-based platforms. For example, if the operating system locale setting is en_US.UTF-8, then the corresponding NLS_LANG environment variable should be set to AMERICAN_AMERICA.AL32UTF8.

Operating System Locale	`NLS_LANG` Values
French (France)	FRENCH_FRANCE.WE8ISO8859P15 FRENCH_FRANCE.WE8ISO8859P1 FRENCH_FRANCE.WE8MSWIN1252 FRENCH_FRANCE.AL32UTF8
Japanese (Japan)	JAPANESE_JAPAN.JA16EUC JAPANESE_JAPAN.JA16SJIS JAPANESE_JAPAN.AL32UTF8