5 ms·
Any info how this compares to commercial html to pdf renderers like PrinceXML?
by ak39 9y ago
Any info how this compares to commercial html to pdf renderers like PrinceXML?
- defenestration 9y agoI would like to know that as well. We are using wkhtmltopdf for around 2 years. Had many issues with incompatible css. I considered PrinceXML. Looked solid, but a bit expensive and also lacking some css support. I'm considering switching to Puppeteer / Chrome.
- jancurn 9y agoIf you'd like to add specific features, please let me know at jan@apify.com, I'm sure we'll figure it out
- schneidmaster 9y agoIn my experience, Prince is great for static HTML + CSS rendering, but its JavaScript engine is pretty lackluster -- I couldn't get it to work with rendering React components, for example. So it depends a lot on your use case and if you can server-side render everything. It's also pretty pricey[1] -- not that I mind paying for quality software but that sticker could be prohibitive for a lot of folks. [1] https://www.princexml.com/purchase https://www.princexml.com/purchase
- jamespaden 9y agoI'm a developer at https://docraptor.com https://docraptor.com. We're an official Prince partner with a SaaS pricing model, but we've got a separate JavaScript engine for that very reason.
- waddlesworth 9y agoMy main concern is support for the CSS3 Paged Media Module. I have been using PDFReactor for this reason, as wkhtml2pdf and weasyprint have had problems, as will any webkit or chromium based renderer because these layout systems simply do not support paged printing.
- defenestration 9y agoThanks, as a follow-up I found this comparison between PrinceXML and PDFReactor: https://www.print-css.rocks/tools.html https://www.print-css.rocks/tools.html