From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Miller Subject: Re: [PATCH] org-mime: make plain/text mime export a choice Date: Tue, 01 Sep 2015 14:01:43 -0700 Message-ID: References: <87a8t64neo.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47208) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWsgs-00019C-89 for emacs-orgmode@gnu.org; Tue, 01 Sep 2015 17:02:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZWsgn-0002Pa-9B for emacs-orgmode@gnu.org; Tue, 01 Sep 2015 17:02:02 -0400 Received: from mail-pa0-x229.google.com ([2607:f8b0:400e:c03::229]:33749) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWsgm-0002PP-Gv for emacs-orgmode@gnu.org; Tue, 01 Sep 2015 17:01:57 -0400 Received: by pary6 with SMTP id y6so2445652par.0 for ; Tue, 01 Sep 2015 14:01:45 -0700 (PDT) In-reply-to: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: emacs-orgmode@gnu.org Jon Miller writes: > Nicolas Goaziou writes: > >> Hello, >> >> Jon Miller writes: >> >>> Update to how org-mime constructs emails for the plain/text section of the >>> mime email. I've found that using the 'ascii exporter produces a saner >>> plain/text section than using the 'org exporter. Added a new custom variable >>> to control which exporter is used. and changed the default behavior to use >>> 'ascii. Below is my git formatted patch. >> >> Thank you for the patch. >> >> Is there any reason to keep using "org" exporter if "ascii" is superior? >> I.e., what about simply replacing 'org with 'ascii? > > That's a good question. I personally don't think I'd ever need to keep the > plain/text section as org syntax but I wasn't sure about others, so I just > introduced the variable. I suppose the simple replacement would be a simpler > patch. (My org ML subscription is daily digest but have read other replies regarding the latin1 or utf-8 additional options) After trying to include those options, I realized that the export options of latin1 or utf-8 are actually using the same ascii exporter, correct? That is, I can not use either value as-in in the call to (org-export-string-as ...) To support the other options, it appears that we'd have to change the function being used and I'm not sure which direction to take from there. I'd be willing to hack on it further if I could get a hint as to what to use. -- Jon Miller