On 2011-12-02 14:41, Robin Berjon wrote:
On Dec 2, 2011, at 14:00 , Anne van Kesteren wrote:
I tied it to UTF-8 to further the fight on encoding proliferation and encourage
developers to always use that encoding.
That's a good fight, but I think this is the wrong battlefield. IIRC (valid)
JSON can only be in UTF-8,16,32 (with BE/LE variants) and all of those are
detectable rather easily. The only thing this limitation is likely to bring is
pain when dealing with resources outside one's control.
If there's agreement that UTF-8 should be mandated for JSON then this
should apply to *all* of JSON, not only this use case.
Best regards, Julian
