So, as tzwoenn, pointed out, the problem was that you were using
properties files, which are Latin 1 only, and this is enforced by the
JDK. The workaround would be to use an XML formatted properties file,
apparently (though I haven't tested this).
Not sure what the appropriate Mojarra fix is for this - is it
appropriate for JSF to allow UTF-8, despite the Latin 1 requirement?
As far as I can tell, the spec doesn't specify this behavior, though you
could argue it's implicit in the reliance on the properties file.
Please update the 1206 bug you filed with the new info - we may have to
punt this over to the JSF expert group for a mod to the standardization
as well.
Jim
On 7/17/09 1:30 AM, webtier_at_javadesktop.org wrote:
> Figured it out.
>
> In ApplicationResourceBundle.java, there is a method getResourceBundle(Locale).
>
> It loads the resourcebundle like this:
>
> bundle = ResourceBundle.getBundle(baseName, locale, loader);
>
> I have debugged this line, and at this point, no matter what locale is set, characters are screwed up. I have faced this problem before in my applications, and the solution was this article:
>
> http://www.thoughtsabout.net/blog/archives/000044.html
> [Message sent by forum member 'gabox01' (gabox01)]
>
> http://forums.java.net/jive/thread.jspa?messageID=356188
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: webtier-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: webtier-help_at_glassfish.dev.java.net
>