![]() |
With just a little knowledge of locales, resource bundles, and data format classes, you can create a great international application. Like most other internationalized products, your creation would use translated resource strings and would present data to the user using locale-sensitive format objects. That's definitely a big deal, requiring discipline and effort. But you can do better! With just a little more effort, you can create a multilingual application that allows users to switch the user interface (UI) language dynamically. That's on-the-fly, run-time language switching, and it's definitely a hot feature! If you're up to the challenge, you can add this unique capability to your product, making it stand out among its competitors. This article presents a class design that includes a LocaleChooser JavaBean, a LocaleChangeEvent event, and a LocaleChangeListener interface. These three elements are presented to encourage the creation of multilingual, dynamic user interfaces in Java. |
![]() |
When the world wants to talk, it speaks Unicode |
![Program](program2.gif)
![Showcase](showcase2.gif)
![Past Conferences](past2.gif)
![Registration](registration2.gif)
![Unicode Standard](standard2.gif)
![Accommodation](accommodation2.gif)
![Sponsors](sponsors2.gif)
![Talks and Papers](papers2.gif)
![Travel](travel2.gif)
![Conference Board](board2.gif)
![Unicode](topbar1.gif)
![IUC14](topbar2.gif)
International Unicode Conferences are organized by Global Meeting Services, Inc., (GMS).
GMS is pleased to be able to offer the International Unicode Conferences under an exclusive
license granted by the Unicode Consortium. All responsibility for conference finances and
operations is borne by GMS. The independent conference board serves solely at the pleasure
of GMS and is composed of volunteers active in Unicode and in international software
development. All inquiries regarding International Unicode Conferences should be addressed
to info@global-conference.com. Unicode and the Unicode logo are registered trademarks of Unicode, Inc. Used with permission. 23 January 1999, Webmaster |