Summary

With pseudo-localization you first apply an automated simulation of the localization process, followed by building and testing these simulated localized versions to find localizability bugs. Some common bugs include resources that are not exposed to localization; file for mats that are either not in a localizable format, or that have resources that are hard-coded in the source code; string resources that shouldn't be translated; non-Latin characters that cause functional or cosmetic problems; products that cannot be adapted; products that are not mirroring-enabled; string-length extension that causes buffer overflow; string concatenation and a run-time UI that present problems; and strings that are not localized consistently.

Among the most common features in the pseudo-localization process are translation of string resources, string-length extension, dialog box stretching, and replacement of hot keys and shortcut keys with other characters. In addition, you can use pseudo-localization for graphics and audio files, content such as Help files and Web content, and for pseudo-mirroring when working with BiDi languages. By using pseudo-localization in all its capacities, your localizability test will catch potential problems and help ensure high-quality localized products.