Rajendra, the Tester

Localization (L10N) is the process of customizing a software application that was originally designed for a domestic market so that it can be released in foreign markets. This process involves translating all native language strings to the target language and customizing the GUI so that it is appropriate for the target market. Depending on the size and complexity of the software, localization can range from a simple process involving a small team of translators, linguists, desktop publishers and engineers to a complex process requiring a Localization Project Manager directing a team of a hundred specialists. Localization is usually done using some combination of in-house resources, independent contractors and full-scope services of a localization company.

Focused on internationalization and localization aspects of software.

Focusses on 3 aspects:

1. UI testing (A. Translated pieces of texts, B. Various 
names and images which are not translated but are different)

2. Functional testing (remains mostly same/similar in 
different languages)

3. Location specific functionalities including key-strokes 
and use of other hardware)

The 1st and 3rd of the above aspects are mainly termed as 
localization testing.

Localization testing checklist:

- Spelling Rules
- Sorting Rules
- Upper and Lower case conversions
- Printers
- Size of Papers
- Operating System
- Key boards
- Text Filters
- Hot keys
- Mouse
- Date formats
- Measurements and Rulers
- Available memory  
- Voice User Interface language/accent
- Video Content


Localization testing of the UI and linguistics should cover items such as:

• Validation of all application resources.
• Verification of linguistic accuracy and resource attributes.
• Checking for typographical errors.
• Checking that printed documentation, online Help, messages, interface resources, and command-key sequences are consistent with each other. If you have shipped localized versions of your product before, make sure that the translation is consistent with the earlier released versions.
• Confirmation of adherence to system, input, and display environment standards.
• Checking usability of the UI.
• Assessment of cultural appropriateness.
• Checking for politically sensitive content.
• Making sure the market-specific information about your company, such as contact information or local product-support phone numbers, is updated.