Translation Editor Revisited

Christian Stredicke
CEO of Vodia Networks

Some time ago we added the possibility to edit the texts in the web interface and for the emails. Instead of having us translating the items into the various languages, we allow partners in the various regions around the world to help us with truly localized texts that are understandable by clients. The edits can be done right on the web interface; no more Excel tables where texts are translated out of context.

For 5.2.3 we have taken a second look at this. We have now loaded all prompts on our server in the cloud, so that we have a single source for all the translations. The previous solution of mixing local content on the hard drive with the content from the server has shown some weaknesses. Instead of blending the content locally, we now do that on the server. Local changes are included regardless of the question if the author was white-listed by us or not. This makes it possible that the local changes may persist even if a new version comes out.

It seems that over time, some of the languages have suffered. For example, we have seen that Russian texts have somehow made their way into the Turkish translations. We were wondering where and how it could have happened and what we can do. At the end of the day, it seems that the best solution is that users who experience such problems should send us an email and help us with the translations for the country. This way we can not only solve the problems with the wrong language in the wrong place; we can also fill the gaps that come from the new features which have been added over time.