This fixes a lot of the major pain points that pushed me to using Typst in the first place.
It’s too late for me to come back but hopefully this makes someone else’s life a little easier.
9 daysI partially agree. I recently started to heavily use typst for any typesetting where I have enough time to make a template. But as far as I know, typst does not support all the little things LaTeX can do.
For instance
hyperrefcan highlight links so they look different on paper and different in the viewer. Last time I checked, typst backend does not support using those layers.I also have mixed opinions on math syntax. It is great, but current parser implementation really wants you to put in some spaces that make the typing little awkward.
Great plus is proper Unicode support. I remember having trouble citing chinese document names in bibliography, because half of the names wouldn’t use the correct font.
Overall, it’s great, but I don’t consider it to be direct replacement.
I personally never had a case where Typst couldn’t do what I wanted and usually found something better in Typst instead. The only exception is to do curly snake-like rectangle borders, but it’s probably doable in Cetz.
As for hyperref, you are propably right, I would personally use a boolean flag for that and do two versions. Though the whole point of a pdf is to have the same look between it and the print, other features might fail depending on the viewer.
I think the extra spaces in math make it more readable, and it’s kinda the price to pay to not have to add backslashes everywhere. One instance when I found it weird was that
frak("abc")had a different font thanfrak(a b c). So i just make alet abc = $frak( a b c)$rule.I personally never had a case where Typst couldn’t do what I wanted and usually found something better in Typst instead.
Same. I love the structure and syntax. I did not mean to sound a bit like hater. I just wanted to mention that there are niche usecases where you might still need LaTeX.
No worries, you are right. And even if typst was perfect you have to work with other authors or journals that won’t want to use it
- 13 days
the main site has a section on that https://tectonic-typesetting.github.io/en-US/
- Tectonic automatically downloads support files so you don’t have to install a full LaTeX system in order to start using it. If you start using a new LaTeX package, Tectonic just pulls down the files it needs and continues processing. The underyling “bundle” technology allows for completely reproducible document compiles. Thanks to the Dataverse Project for hosting the large LaTeX resource files!
- Tectonic has sophisticated logic and automatically loops TeX and BibTeX as needed, and only as much as needed. In its default mode it doesn’t write TeX’s intermediate files and always produces a fully-processed document.
- The tectonic command-line program is quiet and never stops to ask for input.
- Thanks to the power of XeTeX, Tectonic can use modern OpenType fonts and is fully Unicode-enabled.
- The Tectonic engine has been extracted into a completely self-contained library so that it can be embedded in other applications.
- Tectonic has been forked from the old-fashioned WEB2C implementation of TeX and is developed in the open on GitHub using modern tools like the Rust language.
- Tectonic can be used from Github Actions to typeset your documents whenever a change to them is made:
- setup-tectonic - Use tectonic in your github action workflows (supports caching and optionally biber)
- compile-latex - Thanks to Vinay Sharma for creating the action.
- 12 days
That sounds great! Making LaTeX more accessible is definitely important. In my scientific bubble LaTeX package management was something many people got confused by as well as knowing when to run BibTeX. The available Github Actions definitely makes it easier to not rely on Overleaf too much though it might also be too complicated for some. Cool stuff and thanks for the summary!
