Localization Reader:
Overview of localization

By The ITC SIG of STC

The key steps in any software localization project were identified by Bert Esselink in his article "The Evolution of Localization," published in The Guide from Multilingual Computing and Technology: Localization, available at no charge from http://www.multilingual.com.

The steps in software localization are:

1. Provide a copy of the software build environment to the localization engineers, who perform the remaining steps.
2. Extract files with translatable text.
3. Prepare translation "kits" with specifications and instructions.
4. Support the translators during their work.
5. Merge the translated files with the build environment.
6. Compile localized versions of the software.
7. Resolve "bugs" and test and resize the user interface.

According to Esselink, the steps in localizing online help are:

1. Translate the source HTML files.
2. Compile and test.
3. Include images of the localized application once the application has been translated, built, and tested.

Translation specifications are also provided for the documentation that needs to be translated. Source files in the original language are provided to translators, who are supported in their work by publications personnel.

Internationalization is the basis for ease of localization and includes support of international character sets, separation of localizable features such as translatable character strings from the code, and provision for locale-specific features and functions.

Esselink reports that translators, localization engineers, online and print production personnel, and project managers work together on localization projects. Translation memory technology is a key factor in the success of localization. Software interface localization tools are used to translate and to resize and test the user interface.

Globalization management systems built into content management systems are useful for developing multilingual websites. Software localization requires more direct application of tools and expertise. The lines between website and software development and localization are often not clear. Even print publications can present complex challenges in localization, on account of the sophistication of print publication.

Localization increasingly depends on use of open standards in producing software, web content, and documentation. These standards include XML Localization Interchange File Format (XLIFF) and Translation Memory eXchange (TMX). Using open standards frees writers and translators to concentrate on the words, rather than the publishing or engineering technology.

Product development teams build localization activities into the project plan from the earliest stages. Internationalization of the basic product concept provides the foundation for rapid, effective localization as the release date nears. Products are typically released simultaneously in multiple markets. Therefore translation begins while the source language software is being developed. Translation memory makes it possible to update translations quickly and cost effectively for subsequent versions.