3 ms·
Interesting to compare this to some of the "old school" solutions for converting web pages to PDF such as htmldoc[0] or html2ps[1]. [0] https://github.com/mich
by bm98 9y ago
Interesting to compare this to some of the "old school" solutions for converting web pages to PDF such as htmldoc[0] or html2ps[1].
[0] https://github.com/michaelrsweet/htmldoc https://github.com/michaelrsweet/htmldoc
[1] http://user.it.uu.se/~jan/html2ps.html http://user.it.uu.se/~jan/html2ps.html
- Wilya 9y agoThe old school solutions lack any sort of javascript support (per the docs, htmldoc doesn't even support css), so they wouldn't work for a lot of real world websites. That's not really the same use case. A better comparison would be against the likes of wkhtmltopdf[0], which uses webkit, or the pdf generation features of phantomjs. [0] https://wkhtmltopdf.org/ https://wkhtmltopdf.org/
- j_s 9y agohttps://github.com/wkhtmltopdf/wkhtmltopdf/issues https://github.com/wkhtmltopdf/wkhtmltopdf/issues 1,047 Open 975 Closed Yep, that's about how I remember it. It was such a pain to build on Windows (especially to get a single static binary) that people contributing fixes would often attain hero status by attaching a random binary to an issue. Specifically, GIF support was broken on the official Windows build for 4+ years: https://web.archive.org/web/20140917181225/http://code.google.com/p/wkhtmltopdf/issues/detail?id=441#c41 https://web.archive.org/web/20140917181225/http://code.googl...