- markdown is .txt with just a tiny bit of syntactic sugar/syntax highlighting, and you can export it to pdf or html
- quarto is markdown-but-I-want-to-execute-code-blocks-inside
- typst is latex but modern, with 90% less cruft and 10% less functionality (academia, hating everything modern, will also hate you if you use typst)
- pandoc is how you export to pdf/html/whatever
By and large, it’s obvious which tool is needed when. There’s of course more, like asciidoc, but I struggle to think what isn’t being covered by the markdown/quarto/typst combo. Some wysiwyg editor maybe?
It's okay if this is not the day to day tool used to render, but this should be possible. It's just a compiler between two languages, and latex happens to be Turing complete (and can display arbitrary things to a PDF), so it's 100% in the "not impossible" category
With such a tool nobody has to know if you use typst personally. Just like, say, nobody has to know you use jj rather than git
I chuckled. I'd love to try out typst when the time comes. But for writing a journal paper, it's still going to be latex.
Often supervisors/professors etc will also resist using typst because of the cognitive overhead on their already oversubscribed time. Typst has about 40 years of history to overcome and that will take a long time to do.
Also, it’s possible, using some Pandoc magic², to enjoy aspects of Typst markup while generating a LaTeX document.
It seems like a well designed and thorough superset of markdown.
It can take a long time to draft such comparisons; I crafted one for my own Markdown editor, which uses ConTeXt instead of LaTeX:
https://keenwrite.com/blog/2025/09/08/feature-matrix/
Feel free to use it as a starting point for your own research.
[0]: https://pagedjs.org