.

Overview

These are items to be taken into consideration, the primary goals and layout of the approach to be taken for the localization and globalization process. This is a list of desirables, not an unbending list of required deliverables from which deviation is not permitted.

Design

• In addition to dialogs and bitmaps, all UI strings, menus are loadable resources.
• All non-localizable string constants are separated from localizable strings.
• All string, date, time and number formatting operations are done by locale sensitive functions.
• Executables adapt to language.
• Each module (EXE or DLL) that has a UI has resource only DLL’s for each language.
• A language specific resource only DLL contains dialog box templates, strings and anything else appropriate for its language.

Development

• Developers work in English.

Localization

• Module.RC and Resource.h files from the English development are given to localizers.
• Localizers translate and return new RC file for each language.
• Localized RCs copied into appropriate projects.

Kit Build

• Clean and prepare build area.
• Download latest qualified source.
• Build projects.
• Build installation.

Test

• QA installs kit and selects all languages.
• QA exercises all major languages and as many variations as possible.

Run Time

• When a module starts executing, it checks for the current system locale.
• The appropriate resource only DLL is loaded.
• All localized resources are loaded from the DLL.

Locale Assignment

• Locale assignment is a function of the Control Panel.