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: [Bug] Export Coding System
Date: Fri, 22 Feb 2013 14:19:38 +0100	[thread overview]
Message-ID: <87zjywjxjp.fsf@gmail.com> (raw)
In-Reply-To: <loom.20130222T111457-598@post.gmane.org> (Achim Gratz's message of "Fri, 22 Feb 2013 10:28:13 +0000 (UTC)")

Hello,

Achim Gratz <Stromeko@NexGo.DE> writes:

> I'm exporting an Org file in UTF-8 to LaTeX.  Unless I switch the coding system
> in Emacs from "default" to "UTF-8" (which has the side effect that any new
> buffer will have UTF-8 coding, which is usually not what I want), the LaTeX
> buffer gets created with ISO8859-1/latin-1 encoding (which is dead wrong,
> because several characters in the document are in fact not representable in that
> encoding).  Changing the option "Org Export Latex Coding System" to utf-8
> doesn't change how the LaTeX buffer gets created, but it will then helpfully ask
> when its time to save the buffer if I want to save it as UTF-8 (no, I want it
> created with UTF-8, not changed to a different encoding on save).  That salvages
> a few characters, but the larger damage of \usepackage[latin1]{inputenc} doesn't
> get changed of course.
>
> The coding system of any export buffers should by default follow the Org buffer
> they are created from and any changes to the coding system stipulated by export
> configuration must be applied before the buffer coding system gets used to make
> any decisions on how to export things.

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.

Anyway, with the same context described above, what's the return value
for:

  (detect-coding-string (org-export-as 'latex) t)

in the buffer you want to export?


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-02-22 14:16 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 [this message]
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
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=87zjywjxjp.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
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).