Struggeling with Eclipse…
Recently I was looking into Computer aided translation tools to find a way to improve our current (pretty much non-existent) process of localizing software.
Much to my surprise I had to find out that there is not much choice available. Most free tools (like Pootle) are focused around PO files, while java property files are 2nd class citizens if supported at all. After trying some tools without much success, I decided to create my own tool instead. So after several weeks of late-night work I can proudly announce an early prototype of
The main idea is to tightly integrate the tool into the developers workflow to be as little intrusive as possible. Developers use their favorite IDE to create and edit the template property files and the translators take care of the rest (with a little help from Jabylon). The achieve this, Jabylon has pluggable team providers to interact with the source code repository.
Jabylon will check out the source code and analyze it to extract all translatable property files and. Once the information is processed, translators see which translations are missing and can edit everything in the web UI.
Jabylon will then commit all translations back to the source code repository to make them available to the developers and build server. Periodically the tool will also check for modifications of existing property files or newly created ones and automatically fetch them from the repository to make them available to the translators.
Here is a brief overview over the main features so far:
It is admittedly a very early stage and many features are missing still, but there is a demo instance running if you want to give it a try. Administrative features are disabled in the demo, so you can not check out new projects but I prepared it with Jenkins, JBoss and Archiva from github to have some test data. This is not live data, so feel free to edit all translations.
The project is going to be released eventually under EPL and is currently developed (together with two friends) on github. We would much appreciate feedback on what you like or dislike about the approach.