On 13 Apr 2009, at 23:39, Chris Anderson wrote:
On Mon, Apr 13, 2009 at 3:34 PM, dmi losth...@yandex.ru wrote:
Hello All!
CouchDB now using modified version of mochijson2 for JSON output.
The standard behavior of this library is to accept unicode in all
forms (unicode, utf8, \u) via
On Tue, Apr 14, 2009 at 00:39, Chris Anderson jch...@apache.org wrote:
Any thoughts on how best to do this? Should utf8 be the default, or \u?
Since RFC 4627 says JSON SHALL be encoded in Unicode, and the default
as specified in the RFC is UTF-8, I think utf8 as the default is
better option
Hello All!
CouchDB now using modified version of mochijson2 for JSON output.
The standard behavior of this library is to accept unicode in all forms
(unicode, utf8, \u) via decode/1,
but when unicode is emitted via encode/1 to the client app, all unicode symbols
are converted to \u
On Mon, Apr 13, 2009 at 3:34 PM, dmi losth...@yandex.ru wrote:
Hello All!
CouchDB now using modified version of mochijson2 for JSON output.
The standard behavior of this library is to accept unicode in all forms
(unicode, utf8, \u) via decode/1,
but when unicode is emitted via encode/1
