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 21:36:48 -1000 Message-ID: References: <87boet5vuc.fsf@Rainer.invalid> <87pq35d9yb.fsf@gmail.com> <87r4nlfrb5.fsf@Rainer.invalid> <87mwy8969u.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36164) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tbnp3-0000Pc-Td for emacs-orgmode@gnu.org; Fri, 23 Nov 2012 02:37:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tbnoz-00076u-R6 for emacs-orgmode@gnu.org; Fri, 23 Nov 2012 02:37:13 -0500 Received: from 50-87-16-10.unifiedlayer.com ([50.87.16.10]:41268 helo=oproxy12-pub.bluehost.com) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1Tbnoz-00076Z-It for emacs-orgmode@gnu.org; Fri, 23 Nov 2012 02:37:09 -0500 In-Reply-To: <87mwy8969u.fsf@Rainer.invalid> (Achim Gratz's message of "Fri, 23 Nov 2012 07:34:37 +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 Achim Gratz writes: > Thomas S. Dye writes: >> I don't follow the details of this discussion, but I wonder how >> important AUTO really is? > > I'm afraid I can't follow you=E2=80=A6 > > AFAIK, specifying "AUTO" in the LaTeX header is supposed to be replaced > by whatever the coding system of the LaTeX buffer happens to be when it > gets saved. (I've never used it, so it might work differently.) Yes, I believe the encoding is picked up from the Org buffer, but I might be wrong. > >> 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. > > That is not what I was talking about, however useful it might be. I > have already defined the input encoding "utf8" in my LaTeX header and > want to ensure that the buffer gets saved in that format. As an > extension, if I specify any other encoding for LaTeX, the buffer should > be saved in a matching encoding, independently of the encoding that the > org buffer had. If that's a "downgrade", i.e. not all characters are > encodable in that new system, then what you describe above might become > necessary. Yes, that sounds useful. Thanks for the clarification. All the best, Tom --=20 Thomas S. Dye http://www.tsdye.com