From: tsd@tsdye.com (Thomas S. Dye)
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [org-e-latex] Coding System
Date: Thu, 22 Nov 2012 10:18:13 -1000 [thread overview]
Message-ID: <m1lidto0hm.fsf@tsdye.com> (raw)
In-Reply-To: <87r4nlfrb5.fsf@Rainer.invalid> (Achim Gratz's message of "Thu, 22 Nov 2012 19:03:42 +0100")
Aloha Achim,
Achim Gratz <Stromeko@nexgo.de> 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
next prev parent reply other threads:[~2012-11-22 20:18 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 [this message]
2012-11-23 6:34 ` Achim Gratz
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=m1lidto0hm.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=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).