Freddy,
I did see that...BUT.. what would I need to do to hookup <fmt:setBundle/>
and <fmt:message> to use XML based resource bundles? Is that even possible?
If I can't use <fmt:message> as is, I'll probably just implement my own XML
driven mechanism?
On Tue, Mar 9, 2010 at 3:46 PM, Freddy Daoud <xf2...@fastmail.fm> wrote:
> Another possibility is to use XML:
>
> "The loadFromXML(InputStream) and storeToXML(OutputStream, String,
> String)
> methods load and store properties in a simple XML format. By default the
> UTF-8 character encoding is used, however a specific encoding may be
> specified if required."
>
> Source: http://java.sun.com/javase/6/docs/api/java/util/Properties.html
>
> Cheers,
> Freddy
>
> On Tue, 9 Mar 2010 21:06:24 +0100, "Simon Oxenvad Rasmussen"
> <si...@ibill.dk> said:
> > Hi Ross,
> >
> >
> >
> > I too had the issue some time back - my solution was to convert all the
> > text
> > into unicode charactes in the format \uXXXX using the following site
> > http://itpro.cz/juniconv/ (it's a simple javascript for turing text into
> > the
> > \uXXXX format.).
> >
> >
> >
> > Paste the outcome back into your bundle and then save it again - making
> > sure
> > that it actually saves as a utf8 file (in eclipse: rightclick the file ->
> > properties and set encoding).
> >
> >
> >
> > I hope this helps.
> >
> >
> >
> > Fra: Ross Sargant [mailto:rsarg...@tvrc.com]
> > Sendt: 9. marts 2010 20:53
> > Til: Stripes Users List
> > Emne: [Stripes-users] UTF-8 Resource Bundles
> >
> >
> >
> > 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
>
--
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
