From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: [org-e-latex] Coding System
Date: Fri, 23 Nov 2012 07:34:37 +0100 [thread overview]
Message-ID: <87mwy8969u.fsf@Rainer.invalid> (raw)
In-Reply-To: m1lidto0hm.fsf@tsdye.com
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…
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.)
> 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.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
next prev parent reply other threads:[~2012-11-23 6:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 7:28 [org-e-latex] Coding System Achim Gratz
2012-11-19 13:33 ` Suvayu Ali
2012-11-19 17:22 ` Achim Gratz
2012-11-19 17:46 ` Achim Gratz
2012-11-22 13:49 ` Nicolas Goaziou
2012-11-22 18:03 ` Achim Gratz
2012-11-22 20:18 ` Thomas S. Dye
2012-11-23 6:34 ` Achim Gratz [this message]
2012-11-23 7:36 ` Thomas S. Dye
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mwy8969u.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).