Browse Prior Art Database

Self pseudo translating functionality within an application Disclosure Number: IPCOM000188348D
Original Publication Date: 2009-Oct-01
Included in the Prior Art Database: 2009-Oct-01
Document File: 2 page(s) / 23K

Publishing Venue



This article describes an invention which allows an application to pseudo translated itself. The invention identifies and pseudo translates translatable content, creates and installs language packs containing the pseudo translated content, and then reinitializes the application to use the pseudo translated language packs.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 1 of 2

Self pseudo translating functionality within an application

Disclosed is a system which will allow an application to pseudo translate itself (including code contributed from other sources) in order to facilitate effective internationalization and globalization testing.

Software is becoming more complex where many times an end user may use an application containing components from numerous sources. Examples include Eclipse(tm) and Firefox(tm)--both of which allow users to install "plug-ins" which add additional functionality to the core application. When testing these sorts of applications and plug-ins, one important phase is internationalization testing. Rather than testing the application in all relevant locales and languages, this testing can be synthesized by means of pseudo translation testing. Pseudo translation a process in which each translatable string is replaced with a simulated translation of the string--typically the pseudo translated string is longer and contains non-English characters. Usually pseudo translation of an application occurs as part of a special build, but when the source originates from different open and closed source vendors, it can be difficult if not impossible to create a special pseudo build of each component or plug-in. The invention allows testers to pseudo translate an entire installed application without the need for special pseudo builds.

The invention includes four parts or steps:
1. Find translatable content in the installed application
2. Pseudo translation
3. Create "Language Packs" containing the pseudo translated content
4. Restart the application using the pseudo language packs.

This approach is better than other pseudo translation solutions because:
1. It is not necessary to know which plug-ins require pseudo translation at build or install time
2. It does not require the creation of special builds
3. Pseudo does not "corrupt" builds (there is no risk of accidentally shipping pseudo language packs to customers)
4. It does not require cooperation with the sources of all plug-ins involved in the testing
5. It provides testers with immediate control over pseudo translation algorithm used
6. Because pseudo translation occurs at run time, "linked" plug-ins are also picked up and pseudo translated
7. Allows for "delta" pseudo translation--if add...