Localization Tools

How Localization Tools Can Reduce Translation-Localization Costs?

Software Localization Overview

Translation and localization of a software product for the global market is a very expensive and time consuming process. Statistics shows that the cost of localization to one language may vary from $5,000 to 40,000, which is a considerable expenditure for the budget of a small or mid-sized shareware developer. Is it possible to reduce the localization cost? The answer is "Yes!"

Recently, we have done a research into the impact of using a localization tool on the localization costs and would like to share our findings with you. As an example of a localization tool, we chose to use our Lingobit Localizer. The objective of the research was to calculate time, money and effort savings that come with the use of a localization tool in comparison to traditional methods of translation and localization.

In our research, we used the data on the localization of our own products, and we have done great work with our clients. We analyzed their localization experience before they started to use our software and after, evaluating its effectiveness at different stages, starting from the preparation of the localization-translation project and ending with proofreading and testing.

Areas of research:

Prepare for translation and plan

The opportunity to single out a translation part and an ability to manage translation statuses provided by Lingobit Localizer enables better control over the translation process. It also allows the developer to pay only for necessary translations.

Localizability test

Engineering hours tend to add up during localization, because software may contain errors, preventing the developer to localize it smoothly and quickly. By using Pseudo Translate, the developer can find errors and elements that should be translated but have not been separated from the resource files. Another common type of errors that can be found with Pseudo Translate is errors caused by changing localizable resources when instead of a readable text there is some sort of gibberish displayed by the software. The errors, once identified, may help the developer to find the elements of the software that cause them. This can be easily done with the help of Crash Finder. Instead of hours of debugging and repetitive work, Pseudo Translate and Crash Finder let the developer fix problems quickly from the outset, facilitating a smooth localization process without significant efforts put into the localization process.

Exchange with translators (localization kit)

The automated system of generating translation tasks through self-extracting localization packages facilitates a smooth collaboration between the developer and the translator. The package contains a project file and a special edition of Lingobit Localizer for translators that allows them to create localized files, while the source code is hidden. When the translation is over, it can be integrated to the master project anytime, independently from the development process. The localization kit is great for sending over the internet to a translator in another country where translation costs are lower than in the home country. The use of Translation Memory can considerably reduce the costs of translation.

Translation

Lingobit Localizer has a friendly interface that hides technical details behind, making the localization process as comfortable and straightforward to the translator as possible. Because of this, the developer can hire a translator without any technical skills rather than an expensive localization specialist, who is versed in the specialized localization software.

Translation check

The automated system of validation and crash finder allowed us to considerably reduce the time spent on testing the translated versions and increase the quality of translation.

Integration into build process

In a few hours, the localization was integrated into the scripted build process, making it unnecessary for us to develop and support custom solutions.

Reuse of translation across subsequent releases

Much of the translation work can be leveraged across subsequent releases. By using translation memory, where text is memorized into a database the first time it is translated, each sentence need only be translated by a human translator once. When the text appears again in an update or another document or product, the translator is prompted with the existing translation and can accept the translated text from the database. Only new and modified elements have to be translated. According to our findings, the use of translation memory can lead to savings of 10-50% or more over subsequent releases. By taking advantage of memory tools, the cost of localization decreases and the ROI increases over time.

Translation of documentation

The use of translations that were obtained during the localization ensured the consistency of terminology, which allowed us to improve the quality of documentation translation.

Conclusion

On average, the ROI of localizing the first version was estimated at over 300% when the translation was done to 2-3 languages and over 500% when the translation was done to 5-10 languages. As soon as the subsequent version was translated, the ROI was estimated at 700 and 900 correspondingly. Besides, the time to market was considerably reduced, and the release of the translated versions of the product along with the Sim Ship was ensured. The programmers were no longer heavily involved into localization as they used to in the past. Lingobit Localizer localization tool provided simplicity and accessibility, allowing our customers to quickly enter the global market and improve the sales in other countries, providing quality software in a native language.