On Jan 19, 2012, at 9:07 PM, Tom Lane wrote:
> If his client encoding is UTF8, the value will be letter-perfect JSON
> when it gets to him; and if his client encoding is not UTF8, then he's
> already pretty much decided that he doesn't give a fig about the
> Unicode-centricity of the JSON spec, no?
Don’t entirely agree with this. Some folks are stuck with other encodings and cannot change them for one reason or
another.That said, they can convert JSON from their required encoding into UTF-8 on the client side, so there is a
workaround.
Not that this changes anything, and I agree with the overall direction of the discussion here. I just want to make sure
wekeep in mind folks who don’t necessarily have the freedom to switch to UTF-8. (And I say this as someone who *always*
usesUTF-8!)
David
