According to a survey conducted by Common Sense Advisory on 351 enterprise software buyers in Brazil, Russia, Japan, China, Sweden Germany France and Spain, respondents feel that 33 to 69% of this user cohort lack the language skills to use English-language software.
Then "desirability" indexes of combined factors of localized software, translated information, in-language technical support range from four out five in Sweden to nearly everyone in Germany, Russia and Spain to all buyers in Brazil, China, France and Japan. See Table 1 above.
So, localization matters. On how to achieve it to get your application translated or localized, there are multiple software internationalization practices exist, ranging from primitive way of using arrays and database to store the locale and translations, to utilizing mature libraries such as gettext, resourcebundle, ICU(International Components of Unicode) which handle date and time formats, numeric format, currency symbols, native text collation and translation management more efficiently.
Translation contents integration is another topic, how do you integrate the translation with your code in a CI/CD fashion to enable DevOps by utilizing the service provided from service like zanata.org is important in this agile world.
Ok, before we dive into some of globalization topics in detail, I would like to know how you internationalize and localize your application, I would really appreciate you spend few minutes to answer some of the questions below, thanks!
If you have difficulty visiting the Google Form based survey, please use this alternative survey site http://wj.qq.com/s/797798/de3d .Last updated: August 28, 2020