Long term Latex user here, I've been working on generating automatic invoices in Typst for a year now.
On the plus side:
* Getting structured data into typst is sooo much simpler than into latex. For latex, you basically have to render a template, and have to know all the crazy escaping rules for special characters. In typst, you can just read a json file, and do the rendering in typst.
* Super fast. Love it.
* Mostly very easy to use.
Minus:
* Our invoices are structured as multi-page tables, and widow and orphan prevention in a multi-page table seems to be non-existent. The workarounds we tried were too disruptive (lead to text overlapping other text, for example).
* There's a bug in the Python wrapper that means we sometimes don't get a proper error message when there happens to be an error, then we have to recreate the scenario on the command line to find out what the error was.
* Docs could be better (but are mostly OK)
Overall I'm very happy with typst for this use case.
On the plus side:
* Getting structured data into typst is sooo much simpler than into latex. For latex, you basically have to render a template, and have to know all the crazy escaping rules for special characters. In typst, you can just read a json file, and do the rendering in typst.
* Super fast. Love it.
* Mostly very easy to use.
Minus:
* Our invoices are structured as multi-page tables, and widow and orphan prevention in a multi-page table seems to be non-existent. The workarounds we tried were too disruptive (lead to text overlapping other text, for example).
* There's a bug in the Python wrapper that means we sometimes don't get a proper error message when there happens to be an error, then we have to recreate the scenario on the command line to find out what the error was.
* Docs could be better (but are mostly OK)
Overall I'm very happy with typst for this use case.