How WR Localization Service Works
The idea behind WR Localization Service is to give some control over translations to product users.
Notice that this service does not solve the UI design problem for specific languages. It only tries to solve the need to provide translations from one primary language (such as English but not necessarily) to all other languages.
Vendors define a primary language file with all resource strings in it. Vendors also create a "Translate" link from their product or a product support site to this web site.
Users who wish to add or improve translation of the product click on the "Translate" link and are directed to this site where the primary language resource file is found, together with other translations accumulated so far.
Users then select a language they are localizing into and provide their own translation of all or some of the localization strings. Users can also improve an already existing translation unless it is the primary language file, which is controlled by a software developer.
Users submit their translation and the system sends them a localized resource file and also copies it to the vendor. Users just drop the file into the product installation directory, optionally restart the product, and have it localized instantly, with their own help.
Developers watch localization e-mails coming through. Upon collecting enough input to justify quality they may elect to build a language specific resource out of the translations provided.
 | ||||
|
||||
| ||||
[ March 2, 2006 ]
|
||||
 | ||||
