The localization process with Babylon.NET

Localizing in a release cycle and working with external translators

 

Localization in a release-based development cycle

Software products are developed in releases. Localization needs to be performed not just once but for every release in a continuous localzation process. Babylon.NET fully supports the release cycle with specific features at every stage of the cycle.

1st Release

  1. Create a new Babylon.NET solution, specify the invariant language of your application and add the Visual Studio or Generic projects you need to localize.
  2. Scan the projects for strings to be localized. Babylon.NET automatically excludes strings that need not be translated such as numbers.
  3. Add as many target langauges as you need.
  4. Use Automatic Translation to translate all the strings. Automatic Translation is not perfect but it gives you a good start. Generally at least 25% of the strings are corretly translated.
  5. Review and correct all translations suggested by Automatic Translation.
  6. Use the build in quality management tools to verify the quality of your translation.
  7. Save your translations to a Translation Memory file to reuse them during the next release.
  8. Generate Satellite Assemblies.


Subsequent Releases

  1. Develop the next version of your application without worrying about localization. Freely change and or add strings.
  2. When development is completed scan the projects for new and changed strings. Babylon.NET clearly shows new and changed strings.
  3. Use the Translation Memory feature to automatically and consistently translate new strings using already translated strings.
  4. Use Automatic Translation to translate the remaining new and changed strings.
  5. Review all newly translated strings.
  6. Use the build in quality management tools to verify the quality of your translation.
  7. Save your translations to a Translation Memory file to reuse them during the next release.
  8. Generate Satellite Assemblies.

Working with external translators - Outsourcing translations

No matter how many languages your developers may speak, at some point you'll have to outsource translations to external translators. Babylon.NET includes everything that is needed to outsource translations to external translators and reintegrate all translations into a single solution at the end. Here's how it works.

Handing out the work to translators

  1. Create a translation job for every translator.
  2. Add one or more locales to be translated to every translation job.
  3. Create a translation package for every translation job
  4. Send the translation package (a single file) to each translator along with the download link for the free Babylon.NET Translator Edition.

Translating

  1. The translator opens the Babylon.NET translation package file using the free Babylon.NET Translator Edition.
  2. Using the translation memory feature new and changed strings are automatically translated.
  3. With the help of the Automatic Translation feature all remaining strings are automatically translated.
  4. The translator reviews all automatically translated strings and sets the quality status to "approved".
  5. The translators sends the Babylon.NET translation package back to you.

Merging translations back into your localization solution

  1. Use the "Receive translation" function to import a translation package into your localization solution.

Copyright 2016 by Redpin - The localization experts | .NET and Localization. | Download | Buy | Privacy | Contact