Internationalization road hazards
Avoid subtle hindrances to software globalization
From the developerWorks archives
Date archived: May 15, 2019 | First published: August 16, 2005
Support in the Java™ language for multilingual and multicountry environments is strong, but it's not foolproof. If you're not careful, mistaken assumptions in three key areas can make their way into your code and cause it to be U.S.-centric. This article identifies these internationalization gotchas and gives you some techniques to help your applications become more usable across the globe.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.