From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: [Bug] Export Coding System
Date: Sat, 23 Feb 2013 14:31:12 +0100 [thread overview]
Message-ID: <87bobbw40v.fsf@Rainer.invalid> (raw)
In-Reply-To: 87zjyvi3rd.fsf@gmail.com
Nicolas Goaziou writes:
>> Not for LaTeX export AFAICS, ox-latex doesn't seem to use
>> org-export-coding-system. But that'd arguably be a bug in ox-latex,
>> then (more specifically org-latex-guess-inputenc),
>
> I don't understand your answer.
>
> My default coding system is utf-8 and inputenc option is AUTO. When
> I eval:
>
> (setq org-export-coding-system 'iso-latin-1)
The LaTeX exporter used to have a custom variable
org-export-latex-coding-system for this. This variable is not evaluated
anymore but still visible in customize due to the fact that the new
exporter didn't override the definition from the old exporter. So it's
no wonder that nothing changes when I customize away on this variable.
The only new exporter that defines its own coding system is currently
the HTML exporter.
> and export some test buffer to LaTeX, with the suggested patch, I get:
>
> \usepackage[latin1]{inputenc}
>
> So it looks like `org-export-coding-system' variable is taken into
> consideration, doesn't it?
Yes, but I was looking at the example in the HTML exporter that would
prefer its own coding system over the general export coding system and
expected to see something similar.
> What fix are you talking about?
Introducing and using a defcustom specifically for LaTeX export (if
anything at all).
> For now, I apply the previous patch.
Please apply the second one, too.
Now I'll have to go and see what twisted ways it takes for the old
exporter defcustoms to show up in customize, they shouldn't have been
there at all.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2013-02-23 13:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 10:28 [Bug] Export Coding System Achim Gratz
2013-02-22 13:19 ` Nicolas Goaziou
2013-02-22 15:06 ` Achim Gratz
2013-02-22 16:23 ` Nicolas Goaziou
2013-02-22 21:29 ` Achim Gratz
2013-02-22 22:09 ` Nicolas Goaziou
2013-02-23 9:29 ` Achim Gratz
2013-02-23 10:31 ` Nicolas Goaziou
2013-02-23 11:35 ` Achim Gratz
2013-02-23 13:00 ` Nicolas Goaziou
2013-02-23 13:31 ` Achim Gratz [this message]
2013-02-23 13:58 ` Nicolas Goaziou
2013-02-23 15:35 ` Achim Gratz
2013-02-26 12:50 ` Achim Gratz
2013-02-26 17:51 ` Achim Gratz
2013-02-27 13:40 ` Nicolas Goaziou
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=87bobbw40v.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).