Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of jchris@gmail.com designates
 209.85.221.112 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=Yb7dUIlHFNXsm0TttPhvLVEl4k6nw9ba7qySOeQ4frtAf3p4FqvHQ//TAYVY5suFw+
         JcxlVavK1eYqv/Q6RROhBcVtDe6juJZ32wlur2zFtUA9aZt+e7OCO7iBf/ms7kVu894C
         tV8JmioJRj+O1cDCVPpBOxV5JYijOo1akxVP0=
MIME-Version: 1.0
Sender: jchris@gmail.com
In-Reply-To: <946031239662050@webmail127.yandex.ru>
References: <946031239662050@webmail127.yandex.ru>
Date: Mon, 13 Apr 2009 15:39:59 -0700
Message-ID: <e282921e0904131539s353a10eoc64ae751da65aacb@mail.gmail.com>
Subject: Re: unicode output representation
From: Chris Anderson <jchris@apache.org>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On Mon, Apr 13, 2009 at 3:34 PM, dmi <losthost@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, \uXXXX) via decode/1,
> but when unicode is emitted via encode/1 to the client app, all unicode symbols are converted to \uXXXX form.
>
> This is done for maximal compatibility. But I suspect, that modern software, which may want to interact with CouchDB, will have no problems with raw UTF8.
>
> Recent version of mochiweb (r99) introduces an optional capability for mochijson2 to emit raw utf8.
> The proposed way is:
>
> Encoder = mochijson2:encoder([{utf8, true}]),
> JSON = Encoder(json())
>
> I have tested this patch (in reduced form) against CouchDB and it seems to be working.
>
> I think, that bringing this option to CouchDB will be a good improvement for developers of international software.
>

Thanks for digging in here.

To avoid incompatibility with old software, we may want to either:

- make this a request time option
- switch intelligently on some http request header

Any thoughts on how best to do this? Should utf8 be the default, or \uXXXX?

Once we have these questions answered, if you put a patch in JIRA[1]
it's likely to be accepted.

[1] http://issues.apache.org/jira/browse/COUCHDB


-- 
Chris Anderson
http://jchrisa.net
http://couch.io