e-business Globalization Solution Design Guide: Getting Started

Chapter 15. Design and development 117

//to convert the value in the source unit to the value in the target unit, and then

return the new value

return convert(value, sourceUnitName, targetUnitName);

}

15.7 Localization

In our working example, localization has three aspects—locale model, GBOs, and localization

packs. GBOs are application-independent, while localization packs are application-specific.

15.7.1 Locale model

Locale model localization pertains primarily to locale-sensitive computing provided by the

ICU4J-based Locale Model Bean. ICU4J also builds and maintains a repertoire of

locale-related information—for example, time zones, date and time format, and number

format. Using ICU4J, localization is accomplished simply by passing user locale as a

parameter into the Locale Model Bean. Culturally correct data is then returned. Therefore,

locale model localization is implemented by the development team.

15.7.2 GBO

GBO localization pertains primarily to the property files accompanying GBO classes (where

locale-sensitive information is stored). GBO localization for a certain locale means collecting

locale-related information required for this GBO and then organizing it into a property file

according to the pre-defined file structure. For example, in GBONameAddressStyle.class

locale-sensitive information for various locales is stored in the Format.properties file—one for

each locale. GBO localization is implemented by the development team as well, though

information collection might require local support.

1

15.7.3 Localization packs

Localization packs are application-specific because they contain all language-dependent

Web content needed for Our Global Travel Shanghai Demo. It is also the last step of

localization in our working example. During the development phase, Our Global Travel

Shanghai Demo prototype was set up in English, so that the English-version localization pack

became our base.

Translation of localization packs

The English localization pack was then sent to IBM's Translation Service Centers (TSCs) in

Brazil, China, Egypt, France, Germany, Israel, Italy, Japan, South Korea, Spain, and Taiwan

to be translated into Portuguese, Simplified Chinese, Arabic, French, German, Hebrew,

Italian, Japanese, Korean, Spanish, and Traditional Chinese respectively.

In our working example, a Readme file containing special requirements relating to the

localization pack translation was delivered to the local TSCs together with the localization

pack itself. Example 15-14 on page 118 illustrates one such readme:

1

Production of localization packs in other language requires full local translation support.

118 e-Business Globalization Solution Design Guide

Example 15-14 Localization pack translation readme file example

The LocalizationPack file comprises all locale-unique information that will be presented

in the user interface.

Please refer to the English site of Our Global Travel Shanghai Demo when you are

translating this file. This will help you get a rough idea about what you are

translating.

Translate punctuations (for example, colons) according to your locale. For example, in

LocalizationPack.xml, notice the placement of the colon in the following sentence:

<Address1>Street Address1:</Address1>

The names and addresses of all airlines, hotels, and agencies are fictitious and only

need be transliterated.

We strongly recommend that translated XML files be encoded in UTF-8 format.

The readme file also contains information and instructions about the use of Translation

Problem Reporting System (TPRS).

A project named Global Travel Shanghai Translation has been opened in the TPRS for

communication purpose while you are doing translation for Our Global Travel Shanghai

Demo. The TSC of your country/region has been added to this project as TSC user

administrator. Please take advantage of TPRS to report problems, share information, and get

help. Since important inquiries and reminders about translation will be posted on TPRS,

prompt access and response is needed during translation and the translation verification test

of Our Global Travel Shanghai Demo.

Following the instructions in the readme file, local TSCs applied various translation tools such

as TranslationManager (TM) to translate the localization pack and report any problems or

bugs via TPRS.

After translation, the TSC returned the translated localization pack to Our Global Travel

Shanghai Demo developer group and also kept a copy for the coming translation verification

test.

Translation verification test

All localization packs were loaded onto the Web server under the same directory accessible

to the application program. TSCs then went through the entire Our Global Travel Shanghai

Demo Web site in their native languages to verify that the translations were done correctly. If

not, they updated the corresponding localization packs and returned them to the developer

group. During this testing phase, TPRS was also used as the communication tool between

local TSCs and the developer group. When all Web pages in every supported language

appeared correct both functionally and culturally, the translation verification test was

considered complete.