Too expensive right now… prepare for internationalization later!

Companies considering internationalization are inevitably faced with one key factor they cannot ignore: cost. Internationalization is expensive. For any application involving complex data and potentially millions of lines of code to work properly across multiple local platforms, the costs of localization will be significant.  As a result, companies sometimes decide against localization after meeting with an internationalization consulting firm because corporate resolve is just not strong enough to take on the challenges (and costs) at that particular moment. Nevertheless, most of these same companies will likely find that internationalization will become a necessity in the not-so-distant future.  The good news: even if a company cannot afford internationalization in their current budget, there are many steps they can take now to prepare for internationalization later, such as gathering locale requirements, learning about Unicode, considering third party components, talking to experienced localization experts, refining their planning, and more.

For more information on this topic also refer to article “What If Internationalization Expectations Exceed Your Budget? – Significantly” by Adam Asnes and learn how your company can save resources, time and money by taking a few proactive steps now in order to make their eventual internationalization easier, less expensive, (and less painful) when the time is right.

Advertisements

One Response

  1. It is really not as hard as this article makes it sound. If developers use resources for all user-visible strings, that is already over half the battle. If on top of that, they also use layouts (for those strings) that do not make rash assumptions about word order, (or provide alternate layouts for different locales), then they are almost done.

    One more thing: the strings should make sense on their own, since the translators often see just the resource file, they don’t see the string in context on the display. So if the strings make sense on their own, the translators can do their job well. If not, then you may have some surprising bloopers in the translation.

Comments are closed.

%d bloggers like this: