7 steps to software localization
Companies are constantly looking for ways to expand their business, and one of the typical ways to increase sales is to create localized versions of software for various markets around the world. In theory, it is simple. However, there are many pitfalls from incorrectly translated text to a program that suddenly stopped working. How to avoid “translation difficulties”?
Always plan localization well before the release of the product to avoid a rush at the last minute. While planning a product release plan, companies should immediately put in time for testing localized software. Localized versions should be tested as thoroughly as the versions in the original language. Full regression testing of all versions is an essential element for creating a quality product.
A step-by-step plan for testing the original version should also be used to test localized software. UI dialogs and performance must be tested and thus prevent delays in testing for the company. Ideally, each translation should be verified by a native speaker in order to avoid language errors.
')
When localizing to the following critical areas, special attention must be paid:
While writing system code it is always better to use Unicode from the very beginning. Thus you can prevent the distortion of the text and save time to correct errors.
The difference in the length of the text in different languages ​​can be dozens, so text boxes should be designed in such a way as to accommodate, if necessary, additional text. Thus, when switching between languages, the translated text will fit into the user interface.
When working with a separate project branch, it is better to use duplicate characters to replace text strings. When using this technique, it is easy to detect all hard-coded elements by searching through a table of text elements.
It makes sense to hire the services of experienced translators to simultaneously translate software and tips. This approach will ensure the completeness and accuracy of the translation of both software and additional documentation.
Software vendors and device manufacturers are looking for ways to integrate third-party software into their products to improve them. But in this case it is always necessary to take readiness for localization into account. This means that all components that you buy from a third party should be ready for localization, and better - already localized into the languages ​​you need.
With the development of the Internet of Things (IoT) and the growing number of “smart” devices that we encounter in everyday life, in transport and at work, the need for localization is also growing, in this situation you should also pay attention to ready-made and time-tested solutions for localization and software monetization (English), the use of which can give a serious advantage over competitors when entering new markets - both in time and cost - and strengthen its reputation.
Put in time for testing
Always plan localization well before the release of the product to avoid a rush at the last minute. While planning a product release plan, companies should immediately put in time for testing localized software. Localized versions should be tested as thoroughly as the versions in the original language. Full regression testing of all versions is an essential element for creating a quality product.
Create a step by step test plan
A step-by-step plan for testing the original version should also be used to test localized software. UI dialogs and performance must be tested and thus prevent delays in testing for the company. Ideally, each translation should be verified by a native speaker in order to avoid language errors.
')
When localizing to the following critical areas, special attention must be paid:
- Date and time formats (including numeric formats)
- Currency
- Keyboard layout
- Ways to sort, align and glue data
- Color schemes, symbols and icons
- Text or images that may seem out of place in a cultural context.
- Legal restrictions
The string encoding must have the ability to localize
While writing system code it is always better to use Unicode from the very beginning. Thus you can prevent the distortion of the text and save time to correct errors.
Additional space is required to expand the text.
The difference in the length of the text in different languages ​​can be dozens, so text boxes should be designed in such a way as to accommodate, if necessary, additional text. Thus, when switching between languages, the translated text will fit into the user interface.
To get rid of hard-coded strings, use the pseudo-localization technique.
When working with a separate project branch, it is better to use duplicate characters to replace text strings. When using this technique, it is easy to detect all hard-coded elements by searching through a table of text elements.
Make sure software and help are localized at the same time.
It makes sense to hire the services of experienced translators to simultaneously translate software and tips. This approach will ensure the completeness and accuracy of the translation of both software and additional documentation.
Ensure that third party software is also translated.
Software vendors and device manufacturers are looking for ways to integrate third-party software into their products to improve them. But in this case it is always necessary to take readiness for localization into account. This means that all components that you buy from a third party should be ready for localization, and better - already localized into the languages ​​you need.
With the development of the Internet of Things (IoT) and the growing number of “smart” devices that we encounter in everyday life, in transport and at work, the need for localization is also growing, in this situation you should also pay attention to ready-made and time-tested solutions for localization and software monetization (English), the use of which can give a serious advantage over competitors when entering new markets - both in time and cost - and strengthen its reputation.
Source: https://habr.com/ru/post/318186/
All Articles