From mboxrd@z Thu Jan 1 00:00:00 1970 From: Achim Gratz Subject: Re: [Bug] Export Coding System Date: Sat, 23 Feb 2013 14:31:12 +0100 Message-ID: <87bobbw40v.fsf@Rainer.invalid> References: <87zjywjxjp.fsf@gmail.com> <87ppzsjp0t.fsf@gmail.com> <87ehg8nika.fsf@Rainer.invalid> <874nh4j91d.fsf@gmail.com> <871uc7xtri.fsf@Rainer.invalid> <87bobbiao8.fsf@gmail.com> <87wqtzw9du.fsf@Rainer.invalid> <87zjyvi3rd.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:50266) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U9FCf-0002DL-Jc for emacs-orgmode@gnu.org; Sat, 23 Feb 2013 08:31:53 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U9FCK-0000ZB-GF for emacs-orgmode@gnu.org; Sat, 23 Feb 2013 08:31:34 -0500 Received: from plane.gmane.org ([80.91.229.3]:52165) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U9FCK-0000Z6-9O for emacs-orgmode@gnu.org; Sat, 23 Feb 2013 08:31:28 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1U9FCb-00051s-1M for emacs-orgmode@gnu.org; Sat, 23 Feb 2013 14:31:45 +0100 Received: from pd9eb5d03.dip.t-dialin.net ([217.235.93.3]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 23 Feb 2013 14:31:45 +0100 Received: from Stromeko by pd9eb5d03.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 23 Feb 2013 14:31:45 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org 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