MULTILIZER - The Software Globalization Company
Developer Zone

Make Localization Lean and Agile

One of Multilizer's most powerful features is the command-line utility -- "Mlbuild". It contains a limited yet the most important set of features for automating any localization process.

Basic command set

Here's a brief description of the basic command-set of Mlbuild:

This command checks if the files to localize have changed. If they have, the Multilizer project is updated and changes are marked.
This command translates the project using the default Translation Memory taht has been defined in Multilizer. Another way to translate a project is to use import command to populate translations.
This command creates an Exchange package ("Localization Kit") with a Multilizer project to translate and optionally Multilizer Translator Edition.
Import (Improved in Multilizer 6.2)
This command is used to import translations that were done in the Exchange Paclage by translator. Or use this command also to import translations from 3rd-party formats, such as TMX for example!
Build (Improved in Multilizer 6.2)
This command builds the localized files. To give more control over the process, Multilizer 6.2 added the possibility to build just one language.

Automation of the process

The Multilizer localization process can be easily automated using the commands above. And this has been done in several companies. Consider the following benefits in this:

  • No time-consuming opening/saving of file and clicking through Wizards
  • Less chances to make human mistakes
  • Make Multilizer work when you're not at work (schedule Multilizer to work at night time).
  • Integrate building of localized versions in your software build process.
  • Manage handling of increasing number of target languages
  • etc.

Sample process

After creating initial Multilizer project, the (semi)automated process could look like this:

  1. Create new build of software
  2. Run batch to Scan and Exchange project; now you've got Exchange Packages with just new strings to translate.
  3. Run batch Import and Build; now you've got localized files that you can send off for validation.
  4. Repeat step 3 until there are no translation relaetd issues left.
  5. Run batch to Build final localized versions for desired languages.

In the process above the project manager has automated the process step by running a set of simple batch files that make Mlbuild automate most of the work. The manager can of course review the project any time with the UI version of Multilizer.

How does it work in real-life cases?

Do you think the process above is utopistic?

Well, take your time to read a real-life case with even more automation and get convinced of the benefits!


All claims and scenarios depicted in this article are based on real customer cases. All features described here are available in Mlbuild of Multilizer 6.2 Enterprise and used currently by customers.

Best of all, this all is available for you today! Go get it!

Links to go
On-line documentation of mlbuild
Real-life article about Multilizer command-line utility