From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: [Bug] Export Coding System
Date: Sat, 23 Feb 2013 10:29:53 +0100 [thread overview]
Message-ID: <871uc7xtri.fsf@Rainer.invalid> (raw)
In-Reply-To: 874nh4j91d.fsf@gmail.com
Nicolas Goaziou writes:
>> No it is not irrelevant, it simply gets set too late in the game: it
>> asks for the new coding system when it is time to save the buffer, while
>> the content of the buffer has been cobbled together while assuming a
>> different coding system. The only way I know (from browsing the
>> documentation) to override the coding system for a buffer that does not
>> yet have a file association is to set that variable directly,
>> preferrably directly after the buffer is created.
>
> Does the following patch fix the problem?
It fixes the problem when the Org buffer encoding is identical to the
encoding for the LaTeX file. It doesn't fix the problem when I want to
export the file in a different encoding (for instance by customizing Org
Export Latex Coding System), that would require a second step of
re-setting the buffer-file-coding-system before using it to determine
what to write into the inputenc option. Other exporters like HTML
probably also have a way (or should have it) to determine the target
coding system independently from the input coding system, so this is not
a LaTeX only exercise.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2013-02-23 9:30 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 [this message]
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
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=871uc7xtri.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).