Hacker News new | ask | show | jobs
by lupire 264 days ago
For your use case, why were you using LaTeX in the first place? That is more surprising than finding a replacement for LaTeX.
4 comments

If you're compiling millions of documents, many with thousands of pages, you probably need something very universal. LaTeX is boring tech, off the shelf, ready to use. It might take some work to figure out the initial setup with regards to templating and everything else, but after that, you can be generally pretty content that it will handle most things you throw at it just fine.
LaTeX is notoriously bad at being boring tech. It has a lot of very rough edges, especially when it comes to longer documents.
And yet this very post positions Typst as a potential alternative to LaTeX. In other words, LaTeX is still in the top position.

Personally I think ConTeXt is a far superior tool, though its documentation is always trailing quite a distance behind its current capabilities.

I am currently preparing to switch to DITA. The learning curve is steeper at the beginning, but I find the overall concept of topic-oriented, information-typed authoring with content reuse very attractive.

Some people might say that writing in XML is annoying, but it isn't if you have a decent XML editor. In my case, it is Emacs nXML mode. Customisation is possible with DITA-OT [1] and plugins, and yes, it is also based on XSLT. Overall, I think DITA is an industry-proven XML powerhouse. It may be boring, but it has huge potential for anyone with advanced documentation requirements.

[0] https://dita-lang.org/dita/archspec/base/introduction-to-dit...

[1] https://www.dita-ot.org/

I’d suggest LaTeX because of its strengths with tables, mathematical notation, and similar content.

LaTeX notation works well for this and can be easily converted to both web and PDF formats.

But compilation speed definitely needs improvement.

On the other hand, how often do you actually need to compile thousands of pages into a single document? That’s really an edge case.

What else would you use to generate PDFs from a text-based template?
20-ish years ago I wrote a system to do that with xslt. Would not recommend.
E.g. Pandoc, universal tool…
You will be surprised to learn that pandoc uses latex for generating the PDF. It's barely hidden:

https://www.pandoc.org/demo/example33/2.4-creating-a-pdf.htm...

I know it ;) But we are talking about how to use something universal. I like pandoc as it is easy to use and… boring.
Your original comment before editing complained about using pdflatex as if it was not part of the pandoc toolchain. It was not about pandoc being universal.
Doesn’t Pandoc just use LaTeX under the hood?
Pandoc works with typst too.
A good XSL-FO impl with docbook or something like that?
Apart from typst, I've used weasyprint.
DITA, see my other comment on level up.
Asciidoctor?
Docbook
ReportLab?