Continuous integration, can it work for software localisation?
May 12, 2010, 23:32 (0 Talkback[s])
No-Size-Fits-All! An Application-Down Approach for Your Cloud Transformation REGISTER >
[ Thanks to An Anonymous Reader for
this link. ]
"At Translate.org.za we want to keep delivering the
best FOSS localisation tools. To do that we've started using
Continuous Integration (CI) in the development of Pootle, Virtaal
and the Translate Toolkit. We're using a tool called Hudson to
manage our CI process.
"Since the tools that we develop are all focused on localisation
we thought, "Wouldn't it be great if we could use CI to
continuously check our translations?". I hope that you will start
to use some of our scripts, or your own, to ensure that
localisation is part of your CI build process. The problem
"Since we build localisation tools we pride ourselves on doing
localisation well. But even we've made a few mistakes along the
way, mistakes like:
* Shipping broken translation files. There is nothing quite as
frustrating as sending out an application that breaks because of a
typo in the translation of a variable. The cost of fixing the issue
and releasing a bug fix build is just too much for a small
development team. We want to focus on cool new features, we'd
rather not fix a bug that we could have caught with CI."