Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • Thank you very much aplaice for your comprehensive and thoughtful answer. You have given me a lot to work with. Commented Jun 21, 2018 at 21:58
  • In the mean time, as a temporary workaround, I have disabled enriched-mode (it does strange things in combination with Markdown) and started using Markdown in a plain text file. I then use Pandoc to convert to HTML. This turns out to be a good way to proof read the work before committing it to the more permanent PDF format. Commented Jun 21, 2018 at 21:58
  • I can then use the "Export as PDF" option in Safari to create a PDF. Or, if I want page numbers, I can print it and us the "Save as PDF" option. There is also a third option built into OS X (I'm still using El Capitan) called "cupsfilter" which can convert an HTML file to PDF. Commented Jun 21, 2018 at 21:59
  • None of the above is a perfect solutions but all have great potential. One of the problems is that the HTML margins are not transferred to the PDF. I'm looking into Print CSS to deal with that. CSS is also the way I handle margins in the HTML file. One could conceivably automate the whole process and apply a key combination to it; either as a macro or perhaps a bit of elisp. I don't know how to do that as of now but, hey, I'm retired. Commented Jun 21, 2018 at 22:00
  • @aplaice: Thanks a million for a great, clean,concise defun that works very well for me. Commented Sep 21, 2020 at 11:17