Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of paul.joseph.davis@gmail.com
 designates 209.85.220.180 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=hF2K5CvMJ+OjN1nWvsbT68/LpHjY151WtKQCbzpg7y9W6rc8v8oz9z1n+qfDXYbKwT
         yYpL8LOcKR29ty0GmIHTBNCXtybNACCJw5z5t3GKhUd/IIIa94mffwgCSTME06CaerMZ
         rljwcjpq7KoId7TvBG1tcHGd+QbJspqgyyCXY=
MIME-Version: 1.0
In-Reply-To: <BANLkTinOwEzNk=EkL=j+9Mmk01X5H7Tpng@mail.gmail.com>
References: <397688.72873.qm@web112116.mail.gq1.yahoo.com>
 <187E079B-E517-4127-A839-09B2AD37B0F6@vpro.nl>
 <BANLkTikf3EoAuuKxqXDJfD7H=z5jvaVJCQ@mail.gmail.com>
 <BANLkTimfzEt+8uuSa6iAsCZQgmT_k2-m-Q@mail.gmail.com>
 <BANLkTinOwEzNk=EkL=j+9Mmk01X5H7Tpng@mail.gmail.com>
From: Paul Davis <paul.joseph.davis@gmail.com>
Date: Thu, 28 Apr 2011 18:19:16 -0400
Message-ID: <BANLkTinUM+H-N2QsY=RTpa2g7SGUfECJuQ@mail.gmail.com>
Subject: Re: CouchDB View Unicode Document
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Apr 28, 2011 at 5:57 PM, Noah Diewald <noah.diewald@gmail.com> wrot=
e:
>> Can someone paste some actual input/output pairs so I have a clue
>> what's going on.
>>
>> Theoretically \uFFFF isn't a valid escape sequence last I checked
>> (don't get me started on 4627 idiocy).
>>
>> The JSON encoder will by default escape data that is non-printable
>> ascii. The few special cased characters mentioned in the JSON spec are
>> backslash escaped (\t \n \" etc) while All other bits are escaped as
>> \uHHHH sequences.
>
> What you're describing is what I'm seeing. I don't think it is a bug,
> just something I don't like because it isn't taking advantage of the
> benefits of unicode. I'd rather see the characters instead of \uHHHH
> sequences. For instance I get "\u00e9" for "=E9". I guess the JSON spec
> says that any character can be escaped but characters in the basic
> multilingual plane don't need to be because the string is utf8. I
> guess I feel that the benefit of utf8 is supposed to be that escaping
> these characters isn't necessary but that they'll appear in an easily
> human readable form. I think from what you said above that I'm not
> experiencing anything that is unexpected but I can supply some input
> and output if it is.
>
> --
> Noah Diewald
> noah.diewald.me
> noahsarchive.net
>

You are exactly correct. I think the general fear with escaping UTF-8
is to make it easier for the JSON to pass through broken
implementations that don't pay attention to possible UTF-8 in string
data. It's possible to throw make that sort of thing configurable but
that would entail quite a bit of consideration on a couple different
fronts.