4 ms·
For my use case[0], I found weasyprint[1] easier to work with than wkthmltopdf, it gives better results (in the sense they look more like what I get when I save
by williamsmj 6y ago
For my use case[0], I found weasyprint[1] easier to work with than wkthmltopdf, it gives better results (in the sense they look more like what I get when I save to PDF using a browser), and it seems to be more actively maintained.
But in the end, I switched[2] to "chrome --headless --print-to-pdf-no-header", since it reproduces browser behavior pretty much by definition and, while it's a colossal dependency, it's also trivial for non-technical users to install.
[0] https://github.com/mikepqr/resume.md https://github.com/mikepqr/resume.md
[1] https://weasyprint.org/ https://weasyprint.org/
[2] https://github.com/mikepqr/resume.md/commit/206a6cbc85fd04569081b602cbc9386b2dd8857e https://github.com/mikepqr/resume.md/commit/206a6cbc85fd0456...
- the_jeremy 6y agoI tried out weasyprint, wkhtmltopdf, and a trial of a paid one (forget which). They all vastly underperformed chrome and firefox's print to PDF functionality, which both worked exactly as expected (i.e., they print it looking like how the page would look under that browser).
- busymom0 6y agoI used jsPDF for my ResumeToPDF site and it worked pretty well. Only thing I sort of had pain with was that I had to include SVG icons in-line in the html/javascript and had to convert them to base64 to be included in the PDF. And same thing for the custom fonts - I had to include base64 of the font TTFs to be embedded in the PDF: https://resumetopdf.com https://resumetopdf.com https://github.com/MrRio/jsPDF https://github.com/MrRio/jsPDF