Re: Proposed Solution to Non-Serializable MessageResources Class

[Michael Westbay]

M$BqU(Bras-san wrote: > - Add localization information in the struts-config.xml file. If one wants > to overide ResourceBundle file search, we could have your proposed syntax > with adapted rules. > <struts-messages default="en_US"> > <locale locale="en_US" > xml:lang="en-US" > file="MyApp.en" /> > <locale locale="es" > xml:lang="es" > file="MyApp.es" /> > </struts-messages> To this idea, I would add encoding="euc-jp" to the locale tag. Then write a LocalizedResourceBundle which will take the file encoding and automatically convert from it to Unicode on getString(). I've written such a LocalizedResourceBundle before which, when initialized, looks for the BundleEncoded key within itself to decide which, if any, encoding to use. That way I can manage my properties files in a text editor friendly format. > - That way, an application can ask the configuration which languages are > supported. You can write a <selectLanguage /> tag that lists the languages > and change the default locale for the user. I really like that idea. But what language will the SELECT text be in? I've generally found that one should have a language selector in 7-bit ASCII or as an image so that people who don't have support for the character set of the page can at least display the language selector. -- Michael Westbay Work: Beacon-IT http://www.beacon-it.co.jp/ Home: http://www.seaple.icc.ne.jp/~westbay Commentary: http://www.japanesebaseball.com/