From mboxrd@z Thu Jan 1 00:00:00 1970 From: tsd@tsdye.com (Thomas S. Dye) Subject: Re: [org-e-latex] Coding System Date: Thu, 22 Nov 2012 10:18:13 -1000 Message-ID: References: <87boet5vuc.fsf@Rainer.invalid> <87pq35d9yb.fsf@gmail.com> <87r4nlfrb5.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:33680) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TbdEM-00034s-H2 for emacs-orgmode@gnu.org; Thu, 22 Nov 2012 15:18:39 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TbdEL-0001eV-AJ for emacs-orgmode@gnu.org; Thu, 22 Nov 2012 15:18:38 -0500 Received: from oproxy9.bluehost.com ([69.89.24.6]:47923) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1TbdEL-0001e1-0L for emacs-orgmode@gnu.org; Thu, 22 Nov 2012 15:18:37 -0500 In-Reply-To: <87r4nlfrb5.fsf@Rainer.invalid> (Achim Gratz's message of "Thu, 22 Nov 2012 19:03:42 +0100") 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: Achim Gratz Cc: emacs-orgmode@gnu.org Aloha Achim, Achim Gratz writes: > Nicolas Goaziou writes: >> Anyway, if you think it's useful to provide a patch, I suggest to >> dynamically bind `org-export-coding-system' in >> `org-e-latex-export-to-latex' before `org-export-to-file' is called. >> You'll have to open "outfile" in order to apply >> `latexenc-find-file-coding-system'. > > Thanks for the pointers. > >> Do you want to provide such patch? > > I'll keep it on my watchlist. Can't make any promises right now, sorry. I don't follow the details of this discussion, but I wonder how important AUTO really is? It seems to me that a sweet setup uses utf-8 in the buffer but exports latin-1 to LaTeX through use of entities and filters (with the new exporter). This can yield a buffer display that isn't complicated by all the LaTeX machinery, and export something that is maximally compatible in the LaTeX world. It is nice on the eyes and avoids encoding incompatibilities on the back-end. All the best, Tom -- Thomas S. Dye http://www.tsdye.com