emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [org-e-latex] Coding System
Date: Thu, 22 Nov 2012 14:49:16 +0100	[thread overview]
Message-ID: <87pq35d9yb.fsf@gmail.com> (raw)
In-Reply-To: <87boet5vuc.fsf@Rainer.invalid> (Achim Gratz's message of "Mon, 19 Nov 2012 18:46:51 +0100")

Hello,

Achim Gratz <Stromeko@nexgo.de> writes:

> I looked at the code/documentation and it seems the intention is to do
> the reverse lookup, that is look at the buffer encoding and decide what
> to give inputenc as argument (when it is specified as "AUTO" in the
> header template).  I maintain that the other way around (looking at the
> header template and deciding the coding system) is probably easier to
> understand and it is also what's already been used by Emacs: see
> latexenc-find-file-coding-system and latex-inputenc-coding-alist.

Emacs also provides `latexenc-coding-system-to-inputenc', so it doesn't
look like one way is more legitimate than the other.

Note that we can have both ways: with AUTO, let coding-system decide and
without AUTO, let inputenc decide. Also, it isn't necessary to change
the global coding system to change the coding system used to write the
file: see `org-export-coding-system'.

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'.

Do you want to provide such patch?


Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2012-11-22 13:53 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 [this message]
2012-11-22 18:03     ` Achim Gratz
2012-11-22 20:18       ` Thomas S. Dye
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=87pq35d9yb.fsf@gmail.com \
    --to=n.goaziou@gmail.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

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).