21–30 of 170 posts
Don’t. Show a web page and open the print dialog, and tell people to save as PDF. All major browsers support this, and the browser HTML to PDF code is the most robust and accurate.
It's very likely to be a massive batch operation of a ton of HTML files that might not even be their own site.
if you are doing html to pdf, you might also need the ability to merge. a few more features and you're better of with a commercial solution.
pandoc --self-contained input.html -o output.htmlpandoc
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.
If you only have HTML to work with, you can also use Flying Saucer[3], which is what KeenWrite uses to preview Markdown documents when rendered as HTML. Flying Saucer uses an open-source version of iText[4] to produce PDF documents (from HTML source docs).
Another possibility is to use pandoc and LaTeX.
[2]: https://keenwrite.com/docs/user-manual.pdf
chrome --headless --disable-gpu --print-to-pdf https://example.com
Edit: it appears so- https://news.ycombinator.com/item?id=15131840