WeasyPrint VS QuestPDF

You can learn more about weasyprint on their website (https://weasyprint.org/ ). It's an open source Python package that can be launched using cli or from Python code.

This is interesting. So it's HTML -> PDF without using Chrome/Puppeteer etc.? Is that correct. It reminds me of https://weasyprint.org/

Weasyprint (by their own admission) have really struggled with a lot of bugs, which isn't surprising if you're allowing arbitrary HTML input - how are you getting on with that?

wkhtmltopdf is not chromium though? "Wk" literally stands for WebKit.

There's also https://weasyprint.org/ which doesn't use any browser engine, but rather a custom renderer.

And both of those (and Prince) can be used as a backend by Pandoc (https://pandoc.org/)

To create our PDF reports, we use a combination of Weasyprint, Jinja, and Plotly charts. To render a report as a PDF, we first have to render all graphs as images.

https://github.com/Kozea/WeasyPrint

> From a technical point of view, WeasyPrint is a visual rendering engine for HTML and CSS that can export to PDF. It aims to support web standards for printing. WeasyPrint is free software made available under a BSD license.

Hmm, I wonder if you could use servo for a similar purpose.

Also see a full web rendering engine (modern HTML+CSS the whole layout engine) made in pure Python, that can export to PDFs: https://github.com/Kozea/WeasyPrint

Is there a reason you didn't consider something like Weasyprint?

https://weasyprint.org

I've gone through a number of systems to convert CV's, business cards, and other docs and it hasn't let me down yet.

You don't _have_ to use a browser. I had very good results with Weasyprint [0]. And there's also PrinceXML [1] if you're willing to pay.

[0]: https://weasyprint.org/

PDF (Portable Document Format) is widely used to save data or send data in a portable, secure format. When it comes to manipulating data into a PDF file or designing a document like an invoice, C# developers often turn to robust libraries. Two popular Libraries for these tasks are IronPDF and QuestPDF. In this article, we'll delve into how to use QuestPDF for HTML to PDF conversion and compare its features with those of IronPDF.

What is QuestPDF? QuestPDF is an open-source .NET library for PDF document generation. It uses a fluent API approach to compose together many simple elements to create complex documents.

QuestPDF looks really good (I haven't used it) but I believe they changed their license recently.

I used that same library it worked great the only issue I had was the users would often have to manually set the scaling to fit to a page. I'm sure I could've fixed this in other ways if I was more competent with CSS but ended up just switching to use https://github.com/QuestPDF/QuestPDF in a backend instead of doing everything in front end.

Give this a try: QuestPDF

I think you should ask these questions in related discussion on Github: https://github.com/QuestPDF/QuestPDF/discussions/491

May I introduce you to QuestPDF!

➡️ James Newton-King ♔ on Twitter: "Coming in .NET 8: Route tooling for ASP.NET Core" / Twitter ➡️ Announcing .NET Community Toolkit 8.1 ➡️ Uno Platform 4.7 – New Project Template, Performance Improvements and more ➡️ C# Advent 2022 Awards | Cross Cutting Concerns ➡️ GitHub - QuestPDF ➡️ DNF Summit 2023 ➡️ .NET Frontend Day

Like many have suggested, I also cast my vote on QuestPDF. No more +50MB library including a Chrome browser to render HTML so a PDF of it can be created, which took 2-3 seconds each time. But with QuestPDF, it's so much faster!