This is a summary of an article written by Adam Asnes of Lingoport. For the full article, visit http://www.lingoport.com/internationalization-management-mistakes
Sometimes the best way to learn is through mistakes you have made in the past. While this may be true in the personal arena, making mistakes in business is costly. Lingoport has seen a number of internationalization mistakes cost companies money in the past. Here’s a list of the top ten problems businesses looking at internationalization need to realize.
- Don’t forget what drives internationalization: new customers in new markets
- Don’t assume internationalization is just an older software legacy issue: no framework, however new, is capable of internationalizing itself.
- Don’t assume you can treat internationalization like any other feature improvement when it comes to source control management.
- Don’t assume internationalization is just a string externalization exercise: the scope of i18n is much greater.
- Don’t wing it on locale: be sure to consider both language and location.
- Don’t create your very own internationalization framework: speak to somebody who has done it before.
- Don’t think that the team internationalizing your software can work without a working build: developers should be able to test as they go.
- Don’t run out of money: projects suffer from underscoping, resulting in costly release delays.
- Don’t use a half thought-out character encoding strategy: use Unicode.
- Don’t use your same testing plan, or just rely on localization testing, when your functional testing needs to grow to include internationalization requirements.
For full details, read the full article here: http://www.lingoport.com/internationalization-management-mistakes