Deploying a Babel Server
Daniel Selman 2700022VQ3 Visits (1744)
I've been enamored of the Eclipse Babel project for a while now so I'm very pleased to have a guest post on Babel by Benoit Nachawati. Benoit recently joined the JRules Rule Studio team. We are currently experimenting with using an internal Babel Server to streamline interactions between developers, the localization team, QA and the build team. Benoit discusses how we succeeded in installing Babel on an in-house LAMP server, uploading all the translated strings for Rule Studio and connecting Babel to our Subversion code repository.
You like Babel Fish? You'll Love Babel!
By Benoit Nachawati
Localization has always been a challenge for software companies -- creating costly overhead due to the interactions between different entities of the company: developers, configuration management, QA, documentation and translators.
On the other hand, addressing the local market with a localized version of your software will give you a great advantage, especially when your target is not tech users but business users. Those people just want to use your software in their native language. Hence our current interest in the Eclipse Babel project!
So, what is Babel?
Babel is an Eclipse project dedicated to supporting translation of Eclipse projects into different locales. Babel already offers three tools to help translation of Eclipse projects:
In this article, I’ll focus on the Babel Translation Server.
Why use Babel?
Babel Translation Server can be seen as a collaborative platform. It provides a unique entry point to allow users to make and share translations. Some of the key features which make Babel very attractive are:
Here are a few screenshots of the Babel interface:
Babel Home Page
Babel Translate Page
Babel Map Files Addition Page
If you don’t have a well defined process for localization in your company, Babel could provide a nice starting point for defining the collaboration required to build localized software. Of course, everything is not perfect, Babel is still in its incubation phase. In particular Babel could benefit from some additional GUI to ease its usage and make it more accessible. For example:
The Babel workflow can be divided into three steps:
The goal of this step is to populate the database with properties files path and its key-value pairs.
The map file processor will checkout each map file entry to a temporary folder and looks for properties files. It will upload (or update) in the database all properties file paths as well as the key-value pairs for each propert file. Unfortunately, Babel doesn’t currently handle the upload of already existing translations for a specific locale.
Users just need to login into the Babel server and access the translation page. From this page, one can provide translation for each string. The GUI is divided in three parts:
The goal of this step is to generate NL packs per language. Currently, Babel provides a script to generate an Eclipse Update Site: it creates one feature per language which contains all plugin fragments. Only strings that are translated will be included. Afterwards, you’ll just need to publish this Update Site on your web server or into a local directory.
Installing a Babel Server
The installation process is well described from the Babel Project wiki page at
My repository is under SVN, how do I integrate it with Babel?
For now, Babel only works with CVS (SVN support is a planned feature). Luckily enough, the CVS support from the map file processor script is just a matter of calling CVS for a checkout with the right CVS repository location. Here is the corresponding line of code from
$command = "cvs -d " . $aStuff['cvsroot'] . " co " . $tagstring . $aElements;
One would naturally expect to just change this line by the appropriate SVN support like for example:
$command = "svn co --username " . $svnusername . " --password " . $svnpassword . " " . $svnURL;
However, Apache does not change its user properly, so
Ultimately, the SVN checkout will be done by the following line of code:
$command = "sudo svn co --username " . $svnusername . " --password " . $svnpassword . " " . $svnURL;
SVN support not only means just changing the cvs command by the svn command but also provide a correct SVN location (url) to checkout from.