Received: by 10.36.33.8 with SMTP id g8mr7725491nzg.1193595845077;
        Sun, 28 Oct 2007 11:24:05 -0700 (PDT)
Return-Path: <technowee...@gmail.com>
Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181])
        by mx.google.com with ESMTP id k36si4213342waf.2007.10.28.11.24.04;
        Sun, 28 Oct 2007 11:24:05 -0700 (PDT)
Received-SPF: pass (google.com: domain of technowee...@gmail.com designates 64.233.166.181 as permitted sender) client-ip=64.233.166.181;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of technowee...@gmail.com designates 64.233.166.181 as permitted sender) smtp.mail=technowee...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by py-out-1112.google.com with SMTP id p76so2485900pyb
        for <rubyonrails-core@googlegroups.com>; Sun, 28 Oct 2007 11:24:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=beta;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        bh=puLNDYBtK7CLVjLmToUnzWadzgOyckcMx7WksJz/Zsw=;
        b=eSBEn8sriIQxczyPCx5RYicZYFey4PGDqzQAKYhrTCTHEl77BjxRPM0XDeWDVQIlg8qMJrA+/ViEjZPHI0z/NUvAMHMu4dxTJ5dC0x4g1G+kw6X27MgukCze3aQMz0mwhoNCB0ZsvtiwpVdSPFC1weU1HllJdVOWASFX2AYx/ao=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=bPiRDjfNSkfoWCy1NdVm8x5UEpF+P0ZPtgYgAfnY4MJ/04ngYlftL+yr62L4ey/dY+oQZzKkFgkq9hsYT+kxpixIK0m5SNRGmpJewuRpKLbvQVjEwm/+AleMrpsUfRr//Xp1OPHtro0uWe4TovTpaYKKufssLTTTQhcKwkqAdjY=
Received: by 10.35.33.5 with SMTP id l5mr6412549pyj.1193595844496;
        Sun, 28 Oct 2007 11:24:04 -0700 (PDT)
Received: by 10.35.22.14 with HTTP; Sun, 28 Oct 2007 11:24:04 -0700 (PDT)
Message-ID: <48fe25b0710281124y76e2f295r7264ab57028cb31d@mail.gmail.com>
Date: Sun, 28 Oct 2007 13:24:04 -0500
From: "Rick Olson" <technowee...@gmail.com>
To: rubyonrails-core@googlegroups.com
Subject: Re: [Rails-core] Re: JSON encoder shouldn't encode "<" and ">" as octals but
In-Reply-To: <550ed32e0bddb62c19fd0910af401...@ruby-forum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <1193548876.936232.316...@e34g2000pro.googlegroups.com>
	 <db22a569e671ad1f68c9835a5111b...@ruby-forum.com>
	 <ef46c93e0710280128l2f593cb0rb9d94e1ddb00a...@mail.gmail.com>
	 <0af74ddc8ed2dad7e1eb358e7e629...@ruby-forum.com>
	 <ef46c93e0710280150p43a6f209h19da087704ca4...@mail.gmail.com>
	 <1193594588.589458.112...@d55g2000hsg.googlegroups.com>
	 <550ed32e0bddb62c19fd0910af401...@ruby-forum.com>

> I like that- it's worth mentioning that the non-compliance issue I'm
> having is with non-browsers choking on the to_json output, not browsers.
> So distinguishing between the two seems like a good compromise, if we
> need one.

I don't...  But we don't do that for HTML so I'm not sure we have to
for JSON (and I think it's pretty rare that JSON is in HTML anyway).
Do you wanna whip up a patch with the right UTF codes?

-- 
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com