On Tue, 22 Nov 2011 22:40:21 -0500, Austin Clements <amdragon at MIT.EDU> 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 at notmuchmail.org > http://notmuchmail.org/mailman/listinfo/notmuch Peace -- Pieter
