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 <m...@nicolasgoaziou.fr> writes: > Hello, > > pierre.techouey...@free.fr (Pierre Téchoueyres) 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Úchoueyres > ^^^ > see > > Regards,
