Oracle9i
Application Server Wireless Edition Configuration Guide
Release 1.1 Part Number A86701_02 |
|
Multi-byte Character Support describes multi-byte character support in Wireless Edition. Each section of this document presents a different topic. These sections include:
This release of Wireless Edition supports single-byte, multi-byte,
and fixed-width encoding schemes which are based on national, international,
and vendor-specific standards.
If the character set is single byte, and that character set
includes only composite characters, the number of characters and the number
of bytes are the same. If the character set is multi-byte, there is generally
no such correspondence between the number of characters and the number
of bytes. A character can consist of one or more bytes, depending on the
specific multi-byte encoding scheme.
A typical situation is when character elements are combined
to form a single character. For example, in the Thai language, up to three
separate character elements can be combined to form one character, and
one Thai character would require up to 3 bytes when TH8TISASCII or another
single-byte Thai character set is used. One Thai character would require
up to 9 bytes when the UTF8 character set is used.
Multi-byte encoding schemes are needed to support ideographic
scripts used in Asian languages like Chinese or Japanese since these languages
use thousands of characters. These schemes use either a fixed number of
bytes to represent a character or a variable number of bytes per character.
In a fixed-width Multi-byte encoding scheme, each character
is represented by a fixed number of n bytes, where n is greater
than or equal to two.
A variable-width encoding scheme uses one or more bytes to
represent a single character. Some Multi-byte encoding schemes use certain
bits to indicate the number of bytes that represent a character. For example,
if two bytes is the maximum number of bytes used to represent a character,
the most significant bit can be toggled to indicate whether that byte is
part of a single-byte character or the first byte of a double-byte character.
In other schemes, control codes differentiate single-byte from double-byte
characters. Another possibility is that a shift-out code is used to indicate
that the subsequent bytes are double-byte characters until a shift-in code
is encountered.
The Personalization Portal receives the encoding for the
text of the site from the setting in the PAPZ logical device, which is
in the repository. The default encoding is VTF-8, which can be used for
both Western European and Asian languages. The portal sets the content
for each page with the encoding specified by the logical device. To change
the default encoding to multi-byte encoding click PAPZ under Logical Devices
in the Service Designer and change the encoding for your particular language.
To set up a Netscape 4.6 web browser to display Multi-byte data:
Localization has been simplified through the use of a property
file called LocalStrings.properties. This file contains text labels
used by screens within various adapters and JSP pages.
Modify the LocalStrings.properties file in the panama_pasm.zip
file in the ORACLE_HOME\panama\tools\ServiceDesigner\lib directory.
Modify the LocalStrings.properties file in the WE_HOME/server/classes/oracle/panama/adapter/webui
directory.
Localization text for these adapters can be found in LocalStrings.properties
files in the WE_HOME/server/classes/oracle/panama/adapter directory. The
sub-directories are specified.
Table
7-1 LocalStrings.properties Files Details
|
Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|