6
Globalization

This chapter includes the following sections:

• Section 6.1, "Overview"

• Section 6.2, "Determining a User's Locale"

• Section 6.3, "Determining the Encoding of a Logical Device"

6.1 Overview

Oracle9iAS Wireless supports multi-locale and multi-encoding. The Wireless server dynamically determines locale and request and response encoding basedon the runtime context.

6.2 Determining a User's Locale

The Wireless Server dynamically determines the appropriate locale of a user by using such locale information as PALocale, the user's preferred locale, the Accept Language header, and the site locale.

PAlocale is a HTTP parameter that specifies the preferred value before login. The possible value for the PAlocale parameter follows the http accept-language header format. For example, PAlocale = en-US. This format is distinct from the java locale format (en_US).

The user's preferred locale is the language preference of a Wireless user, which is set with the User Manager. For more information, see Section 6.2.3.

The Accept Language header is a HTTP protocol parameter which user agents (Web browsers) send with HTTP requests.

Site Locale is an instance-wide default locale of the Wireless Server. For more information, see Section 6.2.4.

6.2.1 After Login

After login, the Wireless Server respects the user's preferred locale.

6.2.2 Before Login

Before login, the Wireless Web Server (ptg/rm), Async Server, Webtool and Wireless Customization each determine the appropriate locale of a user's device.

Table 6-1 illustrates how the Async Server, the Wireless Web Server, the Webtool and Wireless Customization determine the locale of a user. The numeric value indicates the preference for the detection methods in descending order.

Table 6-1 Locale Determination

Method	Async Server	Wireless Web Sever (ptg/rm)	Webtool and Customization
HTTP parameter: PAlocale.	N/A	1	1
Locale of the registered user.	1	2	N/A
Accept-language http header	N/A	3	N/A
Site default locale	2	4	2

6.2.2.1 Wireless Web Server

The Wireless Web Server (ptg/rm) determines the locale of a user in the following order:

1. Use PAlocale (if present).

2. Use the user's preferred locale if the connecting user can be identified through the device id.

3. Use the Accept_Language HTTP header (if present).

4. Use the site default locale.

6.2.2.2 The Webtool and Wireless Customization

The Webtool and Wireless Customization determine the location of a user in the following order:

1. Use PAlocale (if present).

2. Use the site default locale.

6.2.2.3 Async Server

The Async Server determines the location of a user in the following order:

1. Use the user's preferred locale if the connecting user can be identified through the device id.

2. Use the site default locale.

6.2.3 Setting the Locale for a User Profile

You can set a preferred location for a user when you create a user or edit a user profile. If the preferred location is not specified, then the default site locale is used. For more information, see Section 12.3.4 in Chapter 12, "Managing Users".

6.2.4 Setting the Site Locale

From the Site screen (accessed through the OEM console), you can specify the both the default site locale and a list of locales that the site is intended to support. Use a java locale (such as en_US) for the default site locale and for the list of supported locales. For more information, see Section 4.4.2 in Chapter 4, "Server Configuration".

6.3 Determining the Encoding of a Logical Device

The content encoding of a logical device is used to transport of the result of the device type. The default encoding for all shipped logical devices is set to UTF-8. The encoding format of a logical device is that of the Internet Assigned Numbers Authority (IANA).

You use the Service Designer in the Webtool to update the logical device encoding appropriate to your country. For more information, see Section 10.6.2.1 in Chapter 10, "Developing Services".

The following table illustrates how the encoding is determined

Table 6-2 Determining Encoding

Component	Factor
Wireless Web Server	The encoding of the requesting logical device.
Async Server	Determined by the corresponding transport driver.
Webtool and Customization	Encoding of the logical device called `PAPZ'. The default encoding is UTF-8.
Module Service	Use UTF-8 for reading the request and writing the response.
Alert Message	Determined by the corresponding transport driver.

6.3.1 HttpAdapter - Based Service

To encode the request and response of a HTTPAdapter-based service:

6.3.1.1 Encoding for the request of a HTTPAdapter-based Service

When sending the http request to the remote content provider, only the parameters of the HTTPAdapter service are encoded using the input_encoding of the service (if it is specified). Use the encoding format of the IANA (Internet Assigned Numbers Authority) when specifying the value for input_encoding.

6.3.1.2 Encoding for the response of a HTTPAdapter-based Service

Wireless determines the encoding of the response of a HTTPAdapter-based Service in the following order:

1. Charset as part of the content-type header on the response.

2. Input-encoding (if present) of the input parameter of the service.

3. ISO-8859-1 (the default).

6.3.2 Languages Available for On-Line Help

Users can view the online help for the the Wireless Webtool and the Wireless Customization in 29 languages. The site locale, configured through the System Manger, determines the display language.

In this release, the built-in labels and on-line help for the Wireless Webtool and the Wireless system management and monitoring functions display in nine languages.

The Wireless Web Server (ptg/rm) can display the built-in labels in 29 different languages.

6.3.3 Driver Encoding

Each driver handles encoding individually .