On 27 fév, 09:37, Lothar Kimmeringer <[email protected]> wrote:
> jbdhl schrieb:
>
> To be able to read in UTF-8, I defined my own ResourceBundle-implementation
> (quite a hack)

Starting with Java 1.6, you should be able to read resource bundles as
UTF-8 using a ResourceBundle.Control subclass overriding newBundle to
use an UTF-8 Reader instead of InputStream as the argument to the
PropertyResourceBundle ctor.
Not sure it's less hackish, but it avoids the roundtrip between latin1
and utf8. It should also has the advantage of allowing \uXXXX escapes
in your UTF-8 properties files.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to