You need more than just tools and supplies to build a house. Hammer and nails are indispensable, but, before you start hammering together boards, you need to know the house's electrical needs, plumbing placement, and appropriate building codes. Likewise, when building an internationalized Web application, you need to know more than simply what tools the JDK offers to support your efforts. Reader, Locale, and ResourceBundle classes are your tools, but you still must confront other complexities that will drive how you use those tools as you nail together your application. Internationalization and localization are about more than rendering pages in locale-specific languages. They're about building applications to be globally aware from the browser all the way through to the database. In this article, you look at where to address character encoding when building internationalized Web applications, how localization affects data format, and additional internationalization tools provided by Apache Struts. You also learn how to overcome gaps in the standards and in the Struts framework as well as what pitfalls you might face during implementation.Read End-to-end internationalization of Web applications
NOTE: Does anyone in TheServerSide Community have any tips and tricks for i18n?