Monday June 06, 2005

Putting the myths together - what do you get?

Bippity boppity boo.

And now, the summary of the Internationalization Myths (drum roll, please):

1. "Internationalization means externalizing the user interface so the software can be translated."
2. "Translators choose the best phrase in the target language."
3. "The code is in Java and therefore it's internationalized."
4. "My product supports Unicode and therefore it's internationalized."
5. "My product uses open source and so internationalization requirements don't apply."
6. "ISO-8859-1 is the standard encoding for HTML."
7. "All company employees speak English, so only English needs to be supported by internal tools."
8. "Administration interfaces don't need internationalization."
9. "We've never localized this product/module/component/blidget, so it doesn't need internationalization."
10. "We added internationalization in the last release, so we're done."
11. "If something is wrong, our customers will tell us."
12. "My product works in Japanese, therefore it's internationalized."
13. "Internationalization is implemented after the base product is written by a separate group of engineers."
14. "Internationalization is only needed in the software development department."

Tell everyone you know about these myths, and tell them to tell others. It would be such a pleasure never to hear them again! But of course without them we'd have nothing to laugh at. Or would we?

( Jun 06 2005, 09:19:52 AM PDT ) Permalink Comments [1]