Resource Bundles

Last week I delivered a presentation on "Globalizing Your Java Application." The purpose of my talk was to define the various processes and APIs that help ease this task - as well as to emphasize the idea that "internationalizing" your software is a good practice... even when you are only required to support one language.

If you missed this presentation, stay tuned - I've just finished recording it and am in the editing process. It will be available on YouTube very shortly... http://youtube.intertech.com/

In the meantime, you can test your knowledge by answering these questions:

1) What are the three elements that make up a Java Locale?
2) What is the ISO standard that defines available "Variants?"
3) What GUI considerations do you need to make, in regards to localization?
4) What is the difference between "internationalization" and "localization?"
5) What is the purpose of a ListResourceBundle?
6) How do you pass parameters to a PropertyResourceBundle?
7) How do you implement a "locale-agnostic" search or sort algorithm?
8) What happens if you have a resource bundle that is more specific than a user's submitted locale (i.e. a user's locale is "en", and your resource bundle is "en_US")

Answers will follow in my next post...