Closed GoogleCodeExporter closed 9 years ago
Hex escapes are not a part of the JSON specification - or JSON RFC4627.
ParseException is the correct behavior when provided with invalid JSON.
The correct escape in your example is \u0026 instead of \x26.
Note: I am not a developer on this project, or with google.
Original comment by nuutti.k...@gmail.com
on 26 Mar 2009 at 10:57
As Nuutti points out, this is an invalid bug. You need to use the unicode
escape
sequence.
Original comment by inder123
on 27 Mar 2009 at 7:29
Original issue reported on code.google.com by
alexande...@gmail.com
on 24 Mar 2009 at 8:38