Comment by zja
Comment by zja 5 days ago
pandoc
Comment by zja 5 days ago
pandoc
It matters because pandoc is not rendering the website to pdf, it converts the html to latex and then uses a latex engine to render the pdf.
Forgive me but I don’t understand why that matters to you and am trying to understand what the issue with Latex is.
Because lots of things work this way. For example compilers built on LLV uses an intermediate language and Python uses byte code.
I suspect some html to pdf tools go through postScript.
Does pandoc do JavaScript? For stuff that is rendered (I don't want animated, interactive PDFs...).
To reinforce this: pandoc has been the go-to for a long, long time and they have encountered and addressed tons of issues, which is especially important for two underspecified and over-provisioned formats like HTML and pdf.
Go through the revision and bug history to see a sample of issues you're avoiding by using a highly-trafficked, well-supported solution.
The only reason not to use it is when they say they don't support a given feature that you need; and the nice thing there is that they'll usually say it, and have a good reason why.
The other reason to use pandoc is that while you might currently want PDF as your outbound format, you might end up preferring some other format (structured logically instead of by layout); with pandoc that change would be easy.
Finally, pandoc is extensible. If you do find that you want different output in some respect, you can easily write an plugin (in python or haskel or ...) to make exactly the tweak you need.