Open dahanbn opened 6 years ago
I'm stumped by this issue. I don't have this issue myself, but I'm on Linux and I use utf-8 everywhere. At some point in the process, the utf-8 encoded names are interpreted as if they are latin1. I can't really imagine where this would happen.
Could you post the contents of the pandoc-mode output buffer (which is called " *Pandoc output*"
, without the double quotes but with a space at the beginning)? That might help me understand what's going on.
There isn't much output in the *Pandoc output*
buffer:
pandoc.exe: d:/\307mlaut//pandoc-umlaut-test.docx: openBinaryFile: does not exist (No such file or directory)
How do you create the filename?
Pandoc log shows:
==================================================
Tue Dec 19 14:07:04 2017
Calling pandoc with:
pandoc --read=markdown --write=docx --output=d:/Ümlaut//pandoc-umlaut-test.docx
pandoc-umlaut-test.md: Error in pandoc process
I have some issues with using pandoc-mode for files or directories with umlauts.
If I convert the file
TestUmlaute_äöü.md
via pandoc-mode to docx than I get a file namedTestUmlaute_äöü.docx
.If I put a file into a directory with an umlaut than I get the following error message:
Here was the file
TestbriefDaniel.md
in a directory with the nameUmläut
.Because both cases work with running pandoc from SublimeText I guess, somehow there is something wrong with the encoding of the file names and how Emacs or pandoc-mode calls pandoc.exe.
I use pandoc 2.0.2 64 bit on Windows 10 64 bit, with Emacs 25.3.1 64-bit. Pandoc-mode 20171204.1441.