From: Achim Gratz <Stromeko@NexGo.DE>
To: emacs-orgmode@gnu.org
Subject: Re: [Bug] Export Coding System
Date: Fri, 22 Feb 2013 15:06:47 +0000 (UTC) [thread overview]
Message-ID: <loom.20130222T154532-18@post.gmane.org> (raw)
In-Reply-To: 87zjywjxjp.fsf@gmail.com
Nicolas Goaziou <n.goaziou <at> gmail.com> writes:
> IIUC, there is no such thing as a coding system associated to a buffer.
> A coding system only kicks in when doing some I/O operation.
The coding system should be associated with the file the buffer is visiting, but
a fresh buffer still shows a coding system indicator in the modeline even if it
is not (yet) associated with a file. That coding system always seems to be the
default coding system as provided by the language environment.
> Anyway, with the same context described above, what's the return value
> for:
>
> (detect-coding-string (org-export-as 'latex) t)
Depends on what language environment is set to, but with the default setting of
my Emacs (German) it becomes iso-latin-1, independently of what the coding
system in the original Org buffer was.
I think that the export buffer coding system should be explicitly set (via
buffer-file-coding-system, which is automatically buffer-local) to copy the
coding of the parent buffer (or the coding specified via export options if
anything like that exists) so that the default choice of the language
environment doesn't kick in.
Regards,
Achim.
next prev parent reply other threads:[~2013-02-22 15:07 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 [this message]
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
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=loom.20130222T154532-18@post.gmane.org \
--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).