Timeline for How to set utf-8 encoding for *markdown-output* buffer?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 11, 2022 at 4:31 | comment | added | Rusi | @Volodymyr The solution you've used may be the best you could do. But it should ideally not be necessary. (eg on Linux desktops) if your locale is properly set to "Something.UTF8" it should not be needed. | |
| Mar 2, 2019 at 20:09 | comment | added | Volodymyr | To @Stefan: Thank you for your support. I have finally resolved the issue by adding the following into my 'markdown-mode-hook) : (add-to-list 'process-coding-system-alist '("bash" utf-8-unix . utf-8-unix)). | |
| Feb 28, 2019 at 21:36 | comment | added | Stefan | @Volodymyr: that doesn't change the fact that \342\200\231 indicates that the bytes read (in this case from the output of the markdown transformation) were read incorrectly (it should have read it as ’) and that this problem is the source of the error you see when you then try to save the buffer. Hence you need to figure out why Emacs did not interpret those bytes as utf-8 text but as some binary data. Seems like a bug in your mode's C-c C-c C-p command. | |
| Feb 28, 2019 at 19:43 | comment | added | Volodymyr | Sorry, @Stefan, but I can hardly agree with you. The buffer depicted above is not the representation of the file read from the disk, but as a result of I/O operation. The original file is called "README.md", and it does not contain HTML, it rather contains Markdown. What is seen on the screenshot above is an HTML file that is the result of the original markdown transformation through the markdown.pl utility. | |
| Feb 28, 2019 at 13:04 | comment | added | Stefan | @Volodymyr: No, the problem comes long before you try to save the buffer: the problem you see when you try to save is due to the presence of \342\200\231 instead of ’ in the buffer, which itself is due to Emacs reading the file (or the process output if this text comes from a process output) incorrectly. | |
| Feb 28, 2019 at 10:13 | comment | added | Volodymyr | I do not think that the issue is caused by the NUL bytes in markdown-output buffer. In fact, the warning depicted on the above screenshot is shown BEFORE the buffer is written to the disk. I have searched for NUL byte in the original README.md file, there is no NUL byte in it either.\ I believe that the issue is related to the coding system that is set at the moment the IO command is performed. The IO commans that sends the original buffer contents to markdown.pl and receives its output back. | |
| Feb 26, 2019 at 20:35 | history | answered | Stefan | CC BY-SA 4.0 |