In an informal poll conducted by Lingoport, 73% of respondents who have been involved in an internationalization project indicated that their biggest headache during an internationalization project was accounting for quality issues. This data, collected in a recent webinar, stems from a common misconception of i18n being solely about string externalization. While the visual element of a program is certainly important, having an architecture that detects and adapts to the locale of a user is an essential function of an internationalized product. Additionally, localized product quality is affected by code behavior, text layouts (accounting for language-size and layout settings), and images.
Poll data added that 20% of respondents blamed an incorrectly scoped project as their biggest headache for i18n. By conducting a thorough assessment of a code base for internationalization readiness one will understanding which parts of the code need to be refactored and examined will remove the guesswork and lead to a higher quality i18n project.
Further reading:
If you are facing internationalization quality issues, follow @Lingoport for daily i18n tips. Otherwise, contact us and start a discussion about your internationalization goals.
If you enjoyed this article, please consider sharing it!
