Hi,
Does anybody know of a good solution for dealing with the fact that java
property files only support ISO-8859-1 encoding?
I would really prefer that I could have them be UTF-8 and work with them
naturally in different languages (with no need to use the "nativetoascii"
tool) or look at "U" codes in my files.
I'm having trouble using the fmt:message tag with resource bundles that
contain non-ascii unicode characters ( I get garbled output). Other UTF-8
data displays without issue so page encoding, response encoding etc is all
good.
I *think* the problem is that java property files are assumed to be
ISO-8859-1 encoded so the localized values aren't ready correctly from the
file.
Am I the only one that finds this hilarious considering that property files
are touted as the answer to internationalization?
Appreciate any and all suggestions!
--
Ross Sargant
Software Engineer
p: 954-623-6015 x2108
email: rsarg...@tvrc.com
TVR Communications LLC
541 S. State Road 7,Suite 5,Margate, Florida,33068
http://www.tvrc.com
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
