To make sure that application's functionality or GUI will not be broken after the translation a popular technique known as pseudo-translation is used. In pseudo-translation instead of translating it completely, it is translated in a pseudo manner. Now if the product is launched with locale as Japanese it should show the externalized string as given above instead of "Bad Command".
There are utilities to do this job for you, to do pseudo-translation of all the externalized strings of your application. During pseudo-translation you need to make sure that you are doing it roughly according to the rule.
For example, width is normally expanded up to forty percent for the pseudo-translated strings as compare to the English. As stated above, In I18N testing focus is not on the functionality but on the translation and locale related issues. Once all the externalized strings are pseudo-translated, you need to make sure that you have test case for every message or text element present in the system.
Once it is done, same set of test cases can be executed on the properly translated build to make sure that translation is proper. A convenient approach to internationalization testing is to use the technique of pseudo-localization. This technique simulates the process of localizing products, involving many things a localization center does when localizing a product. To pseudo-localize a product:. Also, other files that may be localized should be modified in some way, such as help, text, html and graphics files.
This approach allows you to use the product, including its menus and other GUI objects, without needing to know another language or fully translate the message files. Thanks for the post. It was very interesting and meaningful. Vee Eee Technologies. Post a Comment. Internationalization Testing. Internationalization Testing Introduction World is flat. Contents: Definition Internationalization Pseudo-localization Definition Internationalization is the process of designing and coding a product so it can perform properly when it is modified for use in different languages and locales.
Internationalization In I18N testing, first step is to identify all the textual information in the system. Pseudo-localization A convenient approach to internationalization testing is to use the technique of pseudo-localization. To pseudo-localize a product: Pseudo-translate message files by inserting a specific prefix and suffix into every message.
You can also modify localizable non-message resources, such as font names and colors. Localizable non-message resources should not be translated. To start with, we test numerous combinations of languages and operating systems OS.
Unexpected user experience issues might arise from a new market using commas instead of decimals, different uses of capitals or accents, or problems with commands and responses. Problems become even more complex when software is confronted with new alphabets, grammar rules text reading left to right instead of right to left, for instance and currencies.
Our software engineering and linguistic teams will be there every step of the way, bringing a combination of the right consultancy, automation tools, testing tools, software and IT support and agile localization with an understanding of what is needed to prepare for a new language and new consumer base. Font tchnology. Line and word breaking. Overlay text properties. Localizability overview. Isolate localizable resources.
String handling. Mirroring awareness. UI considerations. Localization overview. Localization elements. Localization tools.
Localization team. Establishing localization guidelines. Content localization. Quality assurance for world-readiness. The world-ready approach to testing.
0コメント