Dear Philippe,
You are right...
If I change the escaped ("\uXXXX") codes to UTF-16, for my example:
String response="{ \"test\" : \"\\u00c1\\u00c9\\u0170\" }"; //"ÁÉÜ" in
UTF-16
All works correctly.
But I found a strange thin too:
If I disable the"\uxxxx" escaping in JSON writer in server side, all works
as expected. But this is not a good idea according to RFC4627 :((((. In
this mode, the JSON string transports the non-printable characters (0xc3,
0x81, 0xc3, 0x89, 0xc5, 0xb0) ("ÁÉÚ" in UTF-8) without any encoding....
:(:(:( GWT JSON parser expands the UTF-8 character correctly, and the alert
displays correct characters.
I think, JSON string transfer the characters in escaped UTF-16 encoding,
but final expands/stores in String in UTF-8. Therefore, if I skip the
UTF-16 escaping, I can send string in UTF-8 in raw (without escaping).
:(:(:(:(
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
