Hi. I got interested by this change, but suddenly only now get a change to test this and I'm actually confused:
$ curl -XPUT http://localhost:5984/db/somedoc -d '{"привет": "\u043c\u0438\u0440"}' -H 'Content-Type: application/json' {"ok":true,"id":"somedoc","rev":"1-d97dcb1c5d13649423ebe8c282544bce"} $ curl http://localhost:5984/db/somedoc {"_id":"somedoc","_rev":"1-d97dcb1c5d13649423ebe8c282544bce","привет":"мир"} What is your case when you get \uXXXX responses? -- ,,,^..^,,, On Sat, Mar 19, 2016 at 6:20 PM, ermouth <ermo...@gmail.com> wrote: > CouchDB normally delivers non-latin chars in JSON encoded as \uXXXX > entities, that is in most cases meaningless overhead. > > Known roundtrip, lists that re-encode responses, is very slow for views and > not applicable to replication traffic at all. > > Good way is to rebuild CouchDB from sources, making these changes: > > 1. Replace mochijson2.erl with > https://github.com/mochi/mochiweb/blob/master/src/mochijson2.erl, that has > critical fix > 2. Change utf8=false to utf8=true at LOC #95 > 3. Recompile CouchDB. > > Voila, now all json responces are utf-8. > > ermouth
