Skip Headers

Oracle9iAS Wireless Administrator's Guide
Release 2 (9.0.4)

Part Number B10685-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Feedback

Go to previous page
Previous
Go to next page
Next
View PDF

5
Globalization

This chapter includes the following sections:

5.1 Overview

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

5.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 5.2.3.

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


Note:

For information on the HTTP accept-language header format, see the HTTP specification of the World Wide Web Consortium (W3C). 


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

5.2.1 After Login

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

5.2.2 Before Login

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

Table 5-1 illustrates how the Asynchronous Server, the Wireless Web Server, the Webtool and Device Portal Access determine the locale of a user. The numeric value indicates the preference for the detection methods in descending order.

Table 5-1 Locale Determination
Method  Asynchronous Server  Wireless web server (ptg/rm)  Webtool and Device Portal Access 

HTTP parameter: PAlocale.  

N/A 

Locale of the registered user. 

N/A 

Accept-language http header  

N/A 

N/A 

Site default locale 

5.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.

5.2.2.2 The Webtool and Device Portal Access

The Webtool and Device Portal Access determine the location of a user in the following order:

  1. Use PAlocale (if present).
  2. Use the site default locale.

5.2.2.3 Asynchronous Server

The Asynchronous 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.

5.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 9.3.4 in Chapter 9, "Managing Users".

5.2.4 Setting the Site Locale

From the Site screen (accessed through the Oracle Enterprise Manager 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 12.4.2 in Chapter 12, "Server Configuration".

5.3 Languages Available for On-Line Help

Users can view the online help for the Wireless Webtool and the Device Portal Access 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 Device Portal Access (ptg/rm) can display the built-in labels in 29 different languages.

5.4 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.

The following table illustrates how the encoding is determined

Table 5-2 Determining Encoding
Component   Factor 

Wireless Web Server 

The encoding of the requesting logical device. 

Asynchronous Server 

Determined by the corresponding transport driver. 

Webtool and Device Portal Access 

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. 

5.5 HttpAdapter - Based Service

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

5.5.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.

5.5.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).

5.6 Driver Encoding

Each driver handles encoding individually.

5.7 Localizing Voice Applications

To localize the voice-enabled applications included with the Oracle Collaboration Suite:

  1. Identify the location of the English audio files. These files are located in the en application subdirectory as noted in Table 5-3.
    Table 5-3 Location of the English Audio Files for Voice-Enabled Applications
    Application  Location 

    Common (Default) 

    ORACLE_HOME/wireless/modules/common/voice/default/en 

    Voice Login 

    ORACLE_HOME/wireless/marconi_voice/voicelogin/audio/en 

    Main Menu 

    ORACLE_HOME/wireless/marconi_voice/mainmenu/audio/en 

    Email 

    ORACLE_HOME/wireless/modules/common/voice/pim/mail/en 

    Address Book 

    ORACLE_HOME/wireless/modules/common/voice/pim/addressbook/en 

    Calendar 

    ORACLE_HOME/wireless/modules/common/voice/pim/calendar/en 

    LDAP 

    ORACLE_HOME/wireless/modules/common/voice/pim/ldap/en 

    IFS 

    ORACLE_HOME/wireless/modules/common/voice/pim/ifs/en 

  2. Using the English audio files as a model, record the exact same set of files in the target language. The names of the files must be same as those in the English language version.
  3. Place the newly recorded, localized audio files into their own locale-specific subdirectory of the application directory. Accomplishing this basically involves first moving up one level in the hierarchy from the en subdirectory and then placing the newly recorded audio files into the appropriate locale-specific directory noted in Table 5-4.
    Table 5-4 Locale-Specific Subdirectories for Applications
    Locale  Directory Name 

    Arabic 

    ar 

    Czech 

    cs 

    Danish 

    da 

    German 

    de 

    Greek 

    el 

    English 

    en 

    Engish-US 

    en_US 

    Spanish 

    es 

    Spanish-Spain 

    es_ES 

    Finnish 

    fi 

    French 

    fr 

    French_Canada 

    fr_CA 

    Hungarian 

    hu 

    Italian 

    it 

    Japanese 

    ja 

    Korean 

    ko 

    Dutch 

    nl 

    Norwegian 

    no 

    Polish 

    pl 

    Portugese 

    pt 

    Portugese - Brazil 

    pt_BR 

    Romanian 

    ro 

    Russian 

    ru 

    Slovak 

    sk 

    Swedish 

    sv 

    Thai 

    th 

    Turkish 

    tr 

    Chinese 

    zh 

    Chinese-Taiwan 

    zh_TW 

5.8 Rebranding the Oracle Logo Icon

The icon of the Oracle logo resides on the mid-tier installation of the Oracle Collaboration Suite at the following locations, specific to each device type:

There is no logo image for WAP devices.

5.8.1 Changing the Logo File Name

To change the file name, you must edit the reference for the logo in the portal.properties file, which also resides on the mid-tier of the Oracle Collaboration Suite.

To edit the reference in portal.properties file

$ORACLE_HOME/wireless/server/classes/messages/oracle/panama/module/common/portal.properties

edit the following key:

modules.common.UI.image.oracle=/modules/images/<logo_name_without_extension>

For example, edit the key as follows:

modules.common.UI.image.oracle=/modules/images/oracle_logo

In addition, you must edit this key in the corresponding properties files of the supported languages. For example, to edit the key for Brazilian Portugese, you must edit the property file portal_pt_BR.properties. Likewise, to edit the key for French, you must edit portal_fr.properties.