From mboxrd@z Thu Jan 1 00:00:00 1970 From: pierre.techoueyres@free.fr (Pierre =?utf-8?Q?T=C3=A9choueyres?=) Subject: Re: [PATCH] Add new keyword :coding for #+include directive Date: Thu, 24 May 2018 23:29:28 +0200 Message-ID: <87a7sooi87.fsf@killashandra.ballybran.fr> References: <87tvsbx72g.fsf@killashandra.ballybran.fr> <87in8qyh3t.fsf@killashandra.ballybran.fr> <874lkakz58.fsf@nicolasgoaziou.fr> <87muy0b4kw.fsf@killashandra.ballybran.fr> <87in8lh3xk.fsf@killashandra.ballybran.fr> <87zi1uqkta.fsf@nicolasgoaziou.fr> <87in8hd7xe.fsf@killashandra.ballybran.fr> <87zi1sl0yq.fsf@nicolasgoaziou.fr> <874lk01ad6.fsf@killashandra.ballybran.fr> <871serrqla.fsf@killashandra.ballybran.fr> <87o9hqrr54.fsf@nicolasgoaziou.fr> <87y3gl6bw7.fsf@killashandra.ballybran.fr> <87d0xrhjp7.fsf@nicolasgoaziou.fr> <87po1rocer.fsf@killashandra.ballybran.fr> <87y3geg4sh.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45293) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fLxnh-0005Yc-FT for emacs-orgmode@gnu.org; Thu, 24 May 2018 17:29:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fLxng-0007el-G9 for emacs-orgmode@gnu.org; Thu, 24 May 2018 17:29:33 -0400 Received: from smtp4-g21.free.fr ([2a01:e0c:1:1599::13]:48996) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fLxng-0007dU-Aw for emacs-orgmode@gnu.org; Thu, 24 May 2018 17:29:32 -0400 In-Reply-To: <87y3geg4sh.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sun, 20 May 2018 09:33:18 +0200") 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" To: Nicolas Goaziou Cc: org-mode Hello Nicolas, I'm sorry for the delay, this problem drove me crazy for a few days. So I started again from the beginning and, of course, I am now unable to replicate my original test case. So, I think you could delete the 0001-Manage-the-encoding-of-files-with-include-.patch patch. I am really sorry for the inconvenience. I hope we can go ahead with the other patch to add a ":coding" keyword to the include directive. To resume the goal: The include keyword works well with encodings like cp850 if, and only if, there are some indications of the encoding in the file (as local variables for example). But sometimes, there is no such information and you can not modify the file (for various reasons. ex: the file is generated automatically). Once again, I'm sorry for the disturbance. Regards, Nicolas Goaziou writes: > Hello, > > pierre.techoueyres@free.fr (Pierre T=C3=A9choueyres) writes: > >> I've used the following command to do the test : >> for emacs 25.3 >> >> #+begin_src sh >> emacs -Q -L lisp -L ~/.emacs.d/elpa-25/htmlize-20180412.1244 -l >> ~/.emacs.d/elpa-25/htmlize-20180412.1244/htmlize-autoloads.el >> testing/examples/test.org >> #+end_src > > With the command above, you're not exporting the file using "ox.el". > What are you testing? Could you use a command that exports the file > (preferably using ASCII (utf-8) export back-end)? > >> TEST WITH DIFFERENT ENCODINGS. >> >> Pierre T=C3=9Achoueyres > ^^^ > see > > Regards,