It is widely recognised that internationalizing software applications can be an extremely challenging and often times, painstaking process. There are a lot of tools out there that are designed to make the process easier, but unfortunately they are not solving the right problem. That is because, until now, the most popular i18n solutions have been solely based on string management. Sure, some of them have really nifty features, but at the core of all these tools, you’ll find a long, bland, unintelligible list of strings.
The problem with those endless lists of undistinctive strings is that they are very very difficult to translate accurately without a lot of help from someone who knows exactly when those strings are used, where and why (usually a developer).
That is precisely why we add context to the core of our i18n tool. In Langur, context means you are translating in your application’s front end directly.
Context allows translators to see the when, the where and the why of the strings they are translating, in the exact same way your users will see them when they use your application. This immediately results in much better quality translations, done considerably faster, with a lot less communications, no file handling and no last minute layout problems.
By providing context, Langur delivers better translations, frees your developer from constant interruptions and saves you time and money.
Also in this blog series: