wkhtmltopdf-windows VS typst

wkhtmltopdf[1] uses the QT WebKit renderer. I used it as part of my job hut work-flow with pandoc to get pdf resumes from markdown. It got me a job, so there's that.

[1] https://wkhtmltopdf.org/

wkhtmltopdf

In 2014 we used wkhtmltopdf[0] to generate PDF copies of Cloudfoundry docs for every version every release, and maybe that's what I'd reach for now. Not sure if Qt WebKit has similar limits as Chromium.

Not that you asked, but I am sitting here silently judging whoever let those pages get that large. Enough html to cap out RAM? Chesterton's Fence dictates that I presume your upstream's hands were tied, but wowee!

0. https://wkhtmltopdf.org/

In most cases no, AsciiDoctor-PDF converter uses the Ruby library PDF library Prawn to generate PDFs, However, there are alternative PDF converters which do convert from HTML (the VSC AsciiDoctor plug-in allows the option to use a different converter), but I don't think they use chrome. Please note that using different pdf converters is a bit of an advanced topic. https://wkhtmltopdf.org/, and asciidoctor-web-pdf.

There are multiple options for how to convert HTML to PDF, one could be by using open-source projects like Puppeteer or wkhtmltopdf. I wrote a separate post How to convert HTML to PDF using Puppeteer, but now for simplicity, I going to use html2pdf.app. Its free plan gives 100 credits per month, excellent!

There are other tools for HTML conversion, such as wkhtmltopdf, but in my experience I've found Chrome to be the easiest to work with.

I remember I used Razor to build HTML that I could then throw into wkhtmltopdf. There is a c# wrapper somewhere on github.

You need to download the Wkhtmltopdf

I read your post 2 days ago and while browsing for some unrelated things I came across https://wkhtmltopdf.org/

https://github.com/typst/typst looks promising, both the language and the tooling. I wonder where it will find its place in a world that is dominated by either Word or LaTex.

I hope in a couple of years we start seeing posts like these with Typst instead of LaTeX. It seems like setting this up would be a bit easier since Typst is much more concise than LaTeX.

[0] https://github.com/typst/typst

For writing math notes (especially in vim), I switch to using Typst (https://typst.app).

Here's a few points:

- The syntax is a lot lighter and easier to type fast. I was up and running in half hour after starting to use it. Once in a while I can look up some symbol name in the docs but that's about it.

- Empty document is a valid document. No preambles, no includes etc, it's all optional and the defaults are sensible. Just start typing.

- It's incremental. Live preview from neovim is in the browser and it's lightning fast, pretty much immediate. No pdf sync pain. No build files, makefiles and all that. Just start typing.

While it's not going to beat latex in terms of serious academic use, for personal use and notes it's close to perfect.

(And of course it's written in Rust...)

Except the main theme, which was HTML export? https://github.com/typst/typst/issues/721

Though it's in the roadmap!

I don't use LaTeX for anything these days but Typst popped up recently and seems like a decent alternative: https://github.com/typst/typst

I am surprised that no one mentions the typst. It is super smooth with typst-preview.

I suggest you ask in the discord channel: https://discord.gg/2uDybryKPe. Or open an issue or question on GitHub: https://github.com/typst/typst