From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id DD3E6429E29 for ; Thu, 12 Jan 2012 09:09:12 -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 MwMqP0RCSw+o for ; Thu, 12 Jan 2012 09:09:12 -0800 (PST) Received: from mail-we0-f181.google.com (mail-we0-f181.google.com [74.125.82.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 4CD4E429E26 for ; Thu, 12 Jan 2012 09:09:12 -0800 (PST) Received: by werm12 with SMTP id m12so1793052wer.26 for ; Thu, 12 Jan 2012 09:09:11 -0800 (PST) Received: by 10.216.136.94 with SMTP id v72mr1924105wei.43.1326388151110; Thu, 12 Jan 2012 09:09:11 -0800 (PST) Received: from localhost ([109.131.126.209]) by mx.google.com with ESMTPS id ga4sm6470978wbb.4.2012.01.12.09.09.09 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 12 Jan 2012 09:09:10 -0800 (PST) From: Pieter Praet To: Austin Clements , Jameson Graef Rollins Subject: Re: [PATCH] Output unmodified Content-Type header value for JSON format. In-Reply-To: <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> <20111123034021.GL9351@mit.edu> User-Agent: Notmuch/0.10.2+115~gadd29f6 (http://notmuchmail.org) Emacs/23.3.1 (x86_64-unknown-linux-gnu) Date: Thu, 12 Jan 2012 18:07:31 +0100 Message-ID: <87ipkglui4.fsf@praet.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: Thu, 12 Jan 2012 17:09:13 -0000 On Tue, 22 Nov 2011 22:40:21 -0500, Austin Clements wrote: > 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. Having missed the IRC discussions: what is the rationale for not including (specific types of?) part content in the JSON output ? Eg. how about inline attached text/x-patch ? > _______________________________________________ > notmuch mailing list > notmuch@notmuchmail.org > http://notmuchmail.org/mailman/listinfo/notmuch Peace -- Pieter