On Jan 22, 2008 11:04 AM, Peter Svensson <[EMAIL PROTECTED]> wrote: > ...My reference page has been this; > http://www.json.org/js.html, and also teh RFC; > http://www.ietf.org/rfc/rfc4627.txt?number=4627 When reading that more > closely, they (or actually he - it's Douglas Crockford :) do actually > mention escaping of characters;...
Ok. > ...However, the pragmatic approach in dealing with shady string is really to > escape them, so that for instance the text; > > foobar; "yohoo!" $bar > > becomes > > foobar%3B%20%22yohoo%21%22%20%24bar... But in that case the client and server have to agree on which values are escaped, right? Is there a standard way in JSON to tell he decoder "pass this value through unescape() first?". -Bertrand
