Bing HongBing HongOSIsoftOSIsoft

Internationalization & Localization @OSIsoft

Agenda

• Internationalization infrastructure– Language Pack approach

– Language Settings Tool

• Localization efforts– Scope

– Use cases

• Prototypes demo– ProcessBook

– WebParts

Internationalization (I18n)

• The process of generalizing a product– Handle multiple languages and cultural conventions without the need

for re-design

– Create one language-neutral core binary with one or more Multilanguage resource dynamic-link libraries (separation of program code and resources)

– Take place at product design and document development phase

• Two key reasons– To ensure product is functional and accepted in international markets

– To ensure product is localizable

Localization (L10n)

• Involves taking a product and making it linguistically and culturally appropriate to the target locale – country/region and language where it will be used and sold

• Localization ≠ Translation– Translation

– In-country language review

– Cultural specifics: format of date, time, currency, number, etc.

– Engineering for all technical aspects

– Testing/Quality assurance

– Desktop publishing

OSIsoft I18n & L10n Strategy

• Internationalize all OSI products to make them ready to be localized whenever market needs– All new products should be internationalized starting at design stage

– Evaluate, prioritize and make plans for existing products to be internationalized

• Focus on a set of primary client products– ProcessBook, ActiveView, DataLink and WebParts

Client Product Localization Scope

• Graphical User Interface elements– Menu items

– Dialog objects

– Text in images

– Messages

• Documentation – Help

– Readme

– User manuals

– Formats: PDF, CHM, HTML and plain text files

Localized vs. English products

• Exactly the same functionalities• Only differences:

– Translated GUI– Translated documents

– Format of cultural data • Number• Currency• Date & Time

– July 4th 2007 (U.S.)– 4th July 2007 (U.K.)– 2007 年 7 月 4 日 (Japan)

Use Cases

English Localized

EnglishLocalized

LocalizedLocalized

1

3

2

Application OS

Localization – Language Pack Approach

Core Product (language

neutral binary + English

Language Pack)

French Language Pack

German Language Pack

Japanese Language Pack

Brazilian Portuguese Language Pack

Simplified Chinese Language Pack

Spanish Language Pack

Benefits

• Time to market– Quick delivery of localized products

• Flexibility– Easy to add new languages

• User experience– Support all three use cases

– Third use case requires a language setting tool

The Problem – Why Language Settings Tool

• Multilingual users in one control room

• English OS in global markets

• English-speaking tech support staff for localized products

Language Pack Installer – First Page

Language Pack Setup (1)

Language Pack Setup (2)

Language Pack Setup (3)

Language Pack Setup (4)

Application Display Language

• Default display language– Set by system admin at installation time

– Per machine basis

• User defined display language– Use Language Settings Tool

– Per user basis

– Need to restart the application to take effect

– Setting applies to all localized OSIsoft desktop applications

Language Settings Tool in Windows Startup

Language Settings Tool in Application

Language Setting Options in the Tool

Select a Language in the Tool

Application Shows the Selected Language

Invoke Language Settings Tool

Select Another Language in the Tool

Application Shows the New Language

Prototype Demo - 1

Brazilian Portuguese ProcessBook

Language Selection at MUI Language Pack Installation

Menus, Trend Configuration & Details

‘Sinusoid' Trend, Details Data & ‘Draw’ Menu

Menu Items – File & Edit Menu

View, Insert & Tools Menu

Draw, Arrange & Window Menu

Menu Items – Help Menu

Prototype Demo - 2

Brazilian Portuguese WebParts

WebParts Home Page

Site Action Menu

Adding a Web Part (1)

Adding a Web Part (2)

Adding a Web Part (3)

Adding a Web Part (4)

Adding a Web Part (5)

Thank You!