https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14251

--- Comment #44 from David Cook <[email protected]> ---
But I've also just been in an extra cranky mood today and commenting at 11:47pm
doesn't help 😅.

I'll try to add some more positive comments...

I used wkhtmltopdf for years as a CLI tool, but I've found in recent years
Webkit doesn't render many webpages very well anymore. Complex
HTML/CSS/Javascript that looks good in Chrome often wouldn't look good in the
Webkit used by wkhtmltopdf. Still... a pretty good tool overall.

Headless Chrome is great, since it's the closest to the Chrome user experience,
but... as a CLI tool it's a bit limited in terms of options. 

My overall preference these days for HTML to PDF is either Puppeteer or
Playwright. While there are bindings out there (not for Perl though I think), I
use Node.js to control them, and I have them use Chrome under the head (stored
in their node_modules directory). I've found these tools to produce the most
accurate outputs. 

However, Puppeteer, Playwright, and Chrome are probably all too heavyweight for
Koha. While I moaned about weasyprint having 500MB of dependencies, they're
mostly Python libraries and low level libraries. And they're all packaged up. 

As Kyle said... if weasyprint works fine then I wouldn't rock the boat.

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to