Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 7647A429E2F for ; Tue, 22 Nov 2011 19:38:03 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DDJKXhBoXDqr for ; Tue, 22 Nov 2011 19:38:03 -0800 (PST) Received: from dmz-mailsec-scanner-6.mit.edu (DMZ-MAILSEC-SCANNER-6.MIT.EDU [18.7.68.35]) by olra.theworths.org (Postfix) with ESMTP id 0367B431FB6 for ; Tue, 22 Nov 2011 19:38:02 -0800 (PST) X-AuditID: 12074423-b7f266d0000008b8-ea-4ecc6a9a1d1b Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id 5A.AE.02232.A9A6CCE4; Tue, 22 Nov 2011 22:38:02 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id pAN3c2Zd004353; Tue, 22 Nov 2011 22:38:02 -0500 Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91]) (authenticated bits=0) (User authenticated as amdragon@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id pAN3c1NU009131 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 22 Nov 2011 22:38:01 -0500 (EST) Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.77) (envelope-from ) id 1RT3h7-0006wg-R7; Tue, 22 Nov 2011 22:40:21 -0500 Date: Tue, 22 Nov 2011 22:40:21 -0500 From: Austin Clements To: Jameson Graef Rollins Subject: Re: [PATCH] Output unmodified Content-Type header value for JSON format. Message-ID: <20111123034021.GL9351@mit.edu> References: <1321659905-24367-1-git-send-email-dmitry.kurochkin@gmail.com> <87fwhkyisj.fsf@servo.finestructure.net> <87wrawq1dz.fsf@gmail.com> <87d3coxu7s.fsf@servo.finestructure.net> <87r512pru2.fsf@gmail.com> <87ipmewo4z.fsf@servo.finestructure.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87ipmewo4z.fsf@servo.finestructure.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuplleLIzCtJLcpLzFFi42IR4hTV1p2VdcbP4M1RNYurW/vZLfbs87K4 fnMmswOzx93TXB47Z91l93i26hZzAHMUl01Kak5mWWqRvl0CV8axg+sZC76wVCxc8J+xgfEn cxcjJ4eEgInEz2O3mCBsMYkL99azdTFycQgJ7GOU6F8yjwnC2cAo0fHrMQuEc5JJ4tW281Bl Sxgl3h+YB9bPIqAqce7HEXYQm01AQ2Lb/uWMILaIgJlEz5c/YDazgJfEhE+nwOqFBYIlXi5r B7N5BbQlWme8YIUY2sok0Xr8ADtEQlDi5MwnLBDNWhI3/r0EauAAsqUllv/jAAlzCphKHHxx AGyOqICKxJST29gmMArNQtI9C0n3LITuBYzMqxhlU3KrdHMTM3OKU5N1i5MT8/JSi3TN9HIz S/RSU0o3MYJCnd1FeQfjn4NKhxgFOBiVeHgjT572E2JNLCuuzD3EKMnBpCTKq5h5xk+ILyk/ pTIjsTgjvqg0J7X4EKMEB7OSCO81d6Acb0piZVVqUT5MSpqDRUmcV2ang5+QQHpiSWp2ampB ahFMVoaDQ0mCd2o8UKNgUWp6akVaZk4JQpqJgxNkOA/Q8Ksgi3mLCxJzizPTIfKnGBWlxHn3 giQEQBIZpXlwvbBU9IpRHOgVYd5mkBU8wDQG1/0KaDAT0OBpa0+ADC5JREhJNTDqp7J0MGUq sb+MYP2y6YJ2mffZciPdD5ndDIsmCi+ZfZk1f+2kt/b7Pl3/uqvcOPzE9klsi8SvmwW27Dy1 5vnzRRLxxd1h3Af+2fEUnf7oXzp3wTXLmow+Pt2eiRxGNSlb19a/81+0f1lURfPR9w9/Trp+ 4uUimTPHJ7wNfbcmo0F93bQfvl9WK7EUZyQaajEXFScCAPK0U3EgAwAA Cc: notmuch@notmuchmail.org X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2011 03:38:03 -0000 Quoth Jameson Graef Rollins on Nov 20 at 12:10 pm: > The open question seems to be how we handle the content encoding > parameters. My argument is that those should either be used by notmuch > to properly encode the content for the consumer. If that's not > possible, then just those parameters needed by the consumer to decode > the content should be output. If notmuch is going to include part content in the JSON output (which perhaps it shouldn't, as per recent IRC discussions), then it must handle content encodings because JSON must be Unicode and therefore the content strings in the JSON must be Unicode.