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: Sat, 23 Feb 2013 11:31:19 +0100	[thread overview]
Message-ID: <87bobbiao8.fsf@gmail.com> (raw)
In-Reply-To: <871uc7xtri.fsf@Rainer.invalid> (Achim Gratz's message of "Sat, 23 Feb 2013 10:29:53 +0100")

[-- Attachment #1: Type: text/plain, Size: 406 bytes --]

Achim Gratz <Stromeko@nexgo.de> writes:

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

Would the following patch work?


Regards,

-- 
Nicolas Goaziou

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-ox-latex-Set-inputenc-option-according-to-org-export.patch --]
[-- Type: text/x-patch, Size: 931 bytes --]

From 2f2591719cc41e7312401ce7368b4bbbdde2c8ad Mon Sep 17 00:00:00 2001
From: Nicolas Goaziou <n.goaziou@gmail.com>
Date: Sat, 23 Feb 2013 11:29:45 +0100
Subject: [PATCH] ox-latex: Set inputenc option according to
 `org-export-coding-system'

* lisp/ox-latex.el (org-latex-guess-inputenc): Set inputenc option
  according to `org-export-coding-system'.
---
 lisp/ox-latex.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el
index cbeaa4e..4047aa2 100644
--- a/lisp/ox-latex.el
+++ b/lisp/ox-latex.el
@@ -946,7 +946,7 @@ when specified inputenc option is \"AUTO\".
 Return the new header, as a string."
   (let* ((cs (or (ignore-errors
 		   (latexenc-coding-system-to-inputenc
-		    buffer-file-coding-system))
+		    (or org-export-coding-system buffer-file-coding-system)))
 		 "utf8")))
     (if (not cs) header
       ;; First translate if that is requested.
-- 
1.8.1.4


  reply	other threads:[~2013-02-23 10:38 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 [this message]
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=87bobbiao8.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).