> but I don't know of a "clean" way to recognize every > available locale from the bundles.
There's no neeed to. There's only going to be one locale active and it's either going to have a translation available or not. The Java runtime manages finding it. > Consider also that Argo could be only partially > translated for a language. That's not a problem. Java manages at least three levels of fallback: 1) country+language, 2) language, 3) default. The sequence is searched for each individual lookup, so you can have partial translations. For example, in Brazil, depending on what resource files are available, you should get: 1) Brazilian Portugese (pt_BR) 2) Portugese (pt) 3) US English 4) the name of property key that was looked up If we get as far as #4, that means there's a bug in our code indicating a mismatch between the names in the code and the names in the language files. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
