How http://www.openl10n.com is used in the localization of Project Wonderland

Project Wonderland is using the newly released open localization tools on http://www.openl10n.com from WeDoGlobalization.com to localize the product into other languages, here is how the tools are being used:

• 1.Initial setup:


• 1.A local Project Wonderland workspace is created on www.openl10n.com
  
• 2.A message database is created for Project Wonderland
  
• 3.Existing translated messages in all l10n files are imported into the databse


• 2. L10n end to end process:


• 1.Check out English files - Check out the latest English files to a local workspace on openl10n.com
  
• 2.Create vendor kits and l10n files - Select a language and create vendor kit with untranslated English messages in that language, and create partially translated but synchronized l10n files with file name of *_lang[_locale].properties
  The vendor kit is very similar with .properties file but with more information like the product name, release number, date created, database to be used, and also the file path name of the message file for each message, each message in the vendor kit is located using the file path name plus the Property or msgid.
  Vendor kit can be downloaded for off line translation using plain text editor or any open sourced or commercial translation tools.
  
• 3.Download vendor kit - Download the vendor kit for offline translation
  
• 4.Translate vendor kits - Translate the messages in a vendor kit online on http://www.openl10n.com
  
• 5.Import vendor kit - After translation, import the vendor kit into the system, this will overwrite the existing translations in the system. After importing a vendor kit, run “create vendor kit and l10n files” to see whether vendor kit is empty which means l10n files are fully translated.
  
• 6.Download l10n files - Download the partially (when vendor kit is not empty) or fully translated l10n files for off line check-in, this should be done manually to make sure no wrong contents are checked in to the workspace.


• 3.L10n bug fixing:


• When an l10n bug is found, such as an untranslated message or a wrong translation. Engineer can login into the system, search the database using file/directory name, English message or existing translation, select the message and edit it, save it and recreate l10n files, download l10n files and check-in to the workspace.


• 4.Reports:


• 1.How many resource files in English and each of other languages.
  
• 2.How many messages in each of the files.
  
• 3.How many words in each of the files.
  
• 4.How many duplicated messages that should be removed or consolidated.
  
• 5.How many messages are the same between English and l10n files,either these messages haven't been translated or they don't need to or shouldn't be translated.


• 5.Other features:


• 1.Create pseudo l10n files - Pseudo l10n files can be created together with vendor kit to do i18n testing while the vendor kit is being translated, some characters will be converted into double bytes and some new double byte characters will be added into each message in the pseudo l10n files except those containing only digits.
  
• 2.Database search - Search the product database using all fields, or search the translations of one message in all languages for whatever purposes.
  
• 3.Glossary - One can easily create a glossary from the database for translators to refer.
  
• 4.Import l10n files - One can upload paired English and l10n files into the database, this is usually used at the beginning of a product database setup.
  
• 5.Add a new entry - This is mainly used to manually fix some problems, not needed in most of the cases.
  
• 6.Leverage – One can decide whether to leverage existing translations from other products on www.openl10n.com when creating the vendor kit, this can significantly reduce the translation efforts when more and more messages from other open sourced projects are added into Open L10n databases.


• 6.More information about www.openl10n.com can be found on http://www.openl10n.com/about.html