From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [BUG] ox-info: incorrect @documentencoding Date: Mon, 11 Nov 2013 10:12:41 +0100 Message-ID: <87eh6nfgja.fsf@gmail.com> References: <20131110134722.GA20321@kuru.dyndns-at-home.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33546) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VfnXv-0005yY-Ox for emacs-orgmode@gnu.org; Mon, 11 Nov 2013 04:12:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VfnXk-0005pg-7W for emacs-orgmode@gnu.org; Mon, 11 Nov 2013 04:12:35 -0500 Received: from mail-ea0-x231.google.com ([2a00:1450:4013:c01::231]:55251) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VfnXk-0005oL-0F for emacs-orgmode@gnu.org; Mon, 11 Nov 2013 04:12:24 -0500 Received: by mail-ea0-f177.google.com with SMTP id f15so2526812eak.22 for ; Mon, 11 Nov 2013 01:12:23 -0800 (PST) In-Reply-To: <20131110134722.GA20321@kuru.dyndns-at-home.com> (Suvayu Ali's message of "Sun, 10 Nov 2013 14:47:22 +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: Suvayu Ali Cc: Emacs Org mode Hello, Suvayu Ali writes: > For the Texinfo exporter, I noticed that the @documentencoding macro is > derived from the buffer-file-coding-system. At the moment it is > translated like this: us-ascii-unix to US-ASCII-UNIX. This makes > makeinfo complain like so: > > org-syntax.texi:5: warning: encoding `US-ASCII-UNIX' is not a canonical texinfo encoding > org-syntax.texi:5: warning: unrecognized encoding name `US-ASCII-UNIX' > > If I manually choose us-ascii as my coding system, Emacs sets it to > us-ascii-unix. I'm guessing us-ascii is an alias of somekind for > us-ascii-. > > Hand editing the US-ASCII-UNIX to US-ASCII in the exported file gets rid > of the warning. This should be fixed. Thank you for reporting it. Regards, -- Nicolas Goaziou