Maintaining changes in development is always more difficult, slower, and expensive If this is not kept in mind, it will lead to translation errors and a confusing experience for your multilingual customers. This becomes even more cumbersome if translators are not provided with any contextual information in relation to the translation and its intended purpose (like screenshots). Your translators likely won’t be going through your UI and trying to figure out where each content key is supposed to be placed, what its function is, and how it will look after translation. Translators still won’t have enough context As you can imagine, this can, and most likely will, distort or break your design and lead to bugs.Įven more so, localization is not just about translating words, your design might not be suitable for other markets for cultural reasons, which can lead to low adoption. Translating from English to Swedish can result in a 20-35% text contraction.įurthermore, it’s important to remember that some languages (such as Hebrew and Arabic) are written from right to left. For example, translating from the English language into German can result in a 20-35% text expansion. Inevitable issues in the best practice l10n workflow Translations impact your designĭifferent languages require different amounts of space in design. However, even though this workflow enables you to automate many parts of your localization process (with the right localization software), this still doesn’t fully save you from issues and delays down the road if the actual translations are planned to be added only after development.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |