- The assumptions and coding style of different developers in the application creates different problems requiring different I18n solutions.
- Multiple teams within your organization develop the various parts of your app, and it is quite time consuming and expensive to collaborate closely for several months until a global release and forever after.
- The programming languages used for different parts of the app determines the mechanisms and tools available for globalization and results in multiple I18n design choices.
- The OS capabilities determine the availability of locale information, and an app needs to make a choice on the extent of its dependency.
- Cultural differences between various regions drive the UI changes, so the UI elements and text layout needs to be flexible.
- Third party tools like databases, application servers and web server engines require different glues and styles of data interchange and integration, and can also impose different implementation decisions on your app.
- Maintaining a common glossary and translations for each language pair you release is important, and keeping them all at the same quality level is complex when dealing with translators spread over the globe, and application code that changes rapidly resulting in new entries every day.
