This appendix describes the following Globalization Support topics:
Installing and Using Oracle Components in Different Languages
Configuring Locale and Character Sets with the NLS_LANG Parameter
This section describes the following features:
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 runtime, each user's Web browser language settings determine the specific language version.
The translated version of Oracle HTML DB should be loaded into a database that has a character set that can support the specific language. If you attempt to install a translated version of Oracle HTML DB into a database that does support the character encoding of the language, the installation may fail or the translated Oracle HTML DB instance may appear corrupt 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 using SQL*Plus. The installation files are encoded in UTF8
.
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 theNLS_LANG
environment variable to AL32UTF8
prior to starting SQL*Plus.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 Oracle Database database character set UTF8 (no hyphen) with 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 "?") is substituted for it. This will terminate parsing and raise an exception.
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, making sure that the character set is AL32UTF8
. For example:
c:\> set NLS_LANG=American_America.AL32UTF8
Start SQL*Plus and connect to the target database as SYS
:
c:\> sqlplus sys/SYS_password as sysdba
Execute the following statement:
SQL> ALTER SESSION SET CURRENT_SCHEMA = FLOWS_010600;
Execute the appropriate language specific script. For example:
SQL> @c:\oracle\product\10.2.0\db_1\htmldb\builder\de\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
. Within each of these directories, there is a language loading script identified by the language code (for example, load_de.sql
or load_ja.sql
).
See Also:
"Installing and Configuring Oracle HTML DB on a Remote Oracle Database" if you need to add languages to an existing Oracle HTML DB on a remote Oracle databaseUse the Add Language option in Oracle Workflow Configuration Assistant to install Oracle Workflow in another language.
See Also:
"Preparing Oracle Workflow Server for the Oracle Workflow Middle Tier Installation" for instructions on starting Oracle Workflow Configuration AssistantOracle Universal Installer runs by default in the selected language of your operating system. You can run Oracle Universal Installer in the following additional languages:
Brazilian Portuguese
German
Japanese
Simplified Chinese
Traditional Chinese
French
Italian
Korean
Spanish
To run Oracle Universal Installer in a different language:
Change the language in which your operating system is running. For example, on Windows 2000:
From the Start menu, select Settings, then Control Panel, then Regional Options.
In the drop-down list, select a language from the preceding table list and choose OK.
Run Oracle Universal Installer by following the instructions in the Oracle Database Installation Guide for Microsoft Windows (32-Bit).
Note:
The selected language is assigned to theNLS_LANG
registry parameter.You can select other languages in which to use Oracle components (such as Oracle Net Configuration Assistant, and 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:
From the installation media: From the installation media, navigate to the companion
directory and double-click setup.exe
.
From an installed Oracle Database Companion CD: From the Start menu, select Programs, then Oracle - HOME_NAME, then Oracle Installation Products, then Universal Installer.
From the Select Installation Type window, select the Product Languages button.
The Language Selection window appears.
Select a language in which to use Oracle components from the Available Languages field.
Use the > arrow to move the language to the Selected Languages field and click OK.
Select appropriate products for installation and click Next.
After installation is complete, the dialog box wording, messages, and online help for the installed components display in the language you selected.
Oracle provides Globalization Support that enables users to interact with a database in their preferred locale and character set settings. The NLS_LANG
parameter 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
parameter is stored in the registry under the HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME
ID
\NLS_LANG
subkey, where ID
is the unique number identifying the Oracle home. This parameter uses the following format:
NLS_LANG
=
LANGUAGE_TERRITORY
.
CHARACTER_SET
where:
Parameter | Description |
---|---|
LANGUAGE |
Specifies the language and conventions for displaying messages, day name, and month name. |
TERRITORY |
Specifies the territory and conventions for calculating week and day numbers. |
CHARACTER_SET |
Specifies the encoding of the database client, which is the character set for data entered or displayed by a client program. |
The following table lists some of the values for the NLS_LANG
parameter:
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 |
See Also:
Oracle Database Installation Guide for Microsoft Windows for more information about how NLS_LANG
works in a Windows installation of Oracle Database
Oracle Database Platform Guide for Microsoft Windows for more information about the subkey locations for multiple Oracle homes
Oracle Database Globalization Support Guide for information about the NLS_LANG
parameter and Globalization Support initialization parameters
The operating system documentation on how to determine the operating system locale environment setting