Introduction to Localization

Applications created to support multiple localized configurations may be managed by creating a separate version for each locale or may be created as a single application with integrated support for multiple local settings. Planning for a globally deployed application includes the following focus topics:

  • Translating user interface (UI) text

  • Translating between character encodings

  • Controlling the direction of text display through mirroring of character data

  • Formatting currency and date values

  • Managing data sorts to include different alphabets

graphics/note_icon.gif

Although it is possible to build multiple versions of an application, each designed to support a particular locale, it is considered a better method to create a single application that supports localized automatic configuration. With multiple versions, there's always the danger that things will get out of synch or that bugs fixed in one version will persist in another.


In this section, we'll look at the overall localization process in more detail, showing you what you need to consider when localizing an application.

The Localization Process

Microsoft divides the process of localization into three primary phases:

  1. Globalization During globalization, you should identify all localizable resources and separate these from the fixed-code portions of the application.

  2. Localizability This process involves ensuring that translating an application from one locale to another will not require design changes.

  3. Localization The process of customizing an application to include new locales, as identified during the Globalization phase.

graphics/alert_icon.gif

The terms globalization, localization, and localizability are often used interchangeably, but they are distinct activities. Watch for questions involving these terms and make sure to identify their function rather than the term specified.


Localization Considerations

An application's user interface (UI) provides many areas that require localization consideration, including the following:

  • Menu item text.

  • Form layout. For example, languages such as German require larger input fields than English because the average word length is longer.

  • Time and date display format.

  • Currency display format.

  • Number display format, such as whether commas are used as the thousands separator.

  • Data-input fields, such as the use of postal codes in countries that do not use the U.S. Zip code standard.

  • Maps, road signs, photos, and other graphics displaying local content.

  • Shortcut keys, including non-Englishbased keyboard support.

  • Calendars, such as managing support for countries that do not use a Gregorian-based calendar.

  • Alphabetical order.

graphics/tip_icon.gif

It is not always necessary to attempt to research every possible configuration setting everywhere in the world. Often, a general-purpose nonlocalized set of input values may be sufficient. Many people worldwide can work with an English-language interface even though they might prefer a translated interface.




Developing and Implementing WindowsR-based Applications with Visual BasicR. NET and Visual StudioR. NET Exam CramT 2 (Exam 70-306)
Developing and Implementing WindowsR-based Applications with Visual BasicR. NET and Visual StudioR. NET Exam CramT 2 (Exam 70-306)
ISBN: N/A
EAN: N/A
Year: 2002
Pages: 188

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net