On 01/19/2012 03:49 PM, Robert Haas wrote:
>
> In other words, let's decree that when the database encoding isn't
> UTF-8, *escaping* of non-ASCII characters doesn't work. But
> *unescaped* non-ASCII characters should still work just fine.
The spec only allows unescaped Unicode chars (and for our purposes that
means UTF8). An unescaped non-ASCII character in, say, ISO-8859-1 will
result in something that's not legal JSON. See
<http://www.ietf.org/rfc/rfc4627.txt?number=4627> section 3.
cheers
andrew
