81–90 of 192 posts
The main problem I have with Typst compared with LaTeX is that it doesn't handle basic fine typographic features, such as the different types of spacing in mathematical mode (mathop, mathbin, mathrel, etc.) or the size of delimiters (big, bigg, etc.)
But then again, apparently so does LaTeX
Earlier quoted context omitted.
Yes, latex's HTML output is fairly good nowadays, after a lot of people made very heroic efforts to put it in a system never intended to support it. Starting a new markup system with no plan for making accessible documents was, in my opinion, a very bad idea. I refuse to use typst until it can produce accessible documents.
> Yes, latex's HTML output is fairly good nowadays, after a lot of people made very heroic efforts to put it in a system never intended to support it. Mind saying more? Didn't know there'd been progress here.
Typst has been pretty amazing, and at my organization, we’re very happy with it. We needed to generate over 1.5 million PDFs every night and experimented with various solutions—from Puppeteer for HTML to PDF conversions, to pdflatex and lualatex. Typst has been several orders of magnitude faster and has a lighter resource footprint. Also, templating the PDFs in LaTeX wasn’t a pleasant developer experience, but with T…
Earlier quoted context omitted.
FWIW there is already partial LaTeX support for Typst via the mitex package: https://github.com/mitex-rs/mitex
This is interesting! However, I suspect general TeX support in Typst is probably impossible unless you re-implement the entirety of TeX within Typst somehow. The TeX language has some really terrible properties. For example, the tokenization rules can be dynamically changed at runtime based on the output that has already been produced. E.g. you can write a TeX file that says "typeset this paragraph, and if the result…
Earlier quoted context omitted.
FWIW there is already partial LaTeX support for Typst via the mitex package: https://github.com/mitex-rs/mitex
This is interesting! However, I suspect general TeX support in Typst is probably impossible unless you re-implement the entirety of TeX within Typst somehow. The TeX language has some really terrible properties. For example, the tokenization rules can be dynamically changed at runtime based on the output that has already been produced. E.g. you can write a TeX file that says "typeset this paragraph, and if the result…
- https://typst.app/universe/package/hydra,
- https://typst.app/universe/package/chic-hdr
- https://typst.app/universe/package/wonderous-book
However I believe this functionality should be available in the typst core.
Earlier quoted context omitted.
Arxiv will accept a rendered pdf, no source files required. Are any special features unlocked if source files are uploaded?
They autoconvert latex to html. Typst can't currently produce html output.
I'm a college student and I use Typst in school all the time. I know I should just use Google Docs/Sheets, but because it's code instead of a WYSIWYG editor it's very easy to create reusable and consistent styles for reports and presentations, and saves time on the long run. (I use polylux module for slides.) Once you get past the learning curve (10-15 hrs if you nosedive) it's incredibly easy to create professional…
Unfortunately out of the box typst is missing an important layout features compared to Latex: the auto-generation of headers (showing the section name in the header). There are some packages that help you with that: - https://typst.app/universe/package/hydra , - https://typst.app/universe/package/chic-hdr - https://typst.app/universe/package/wonderous-book However I believe this functionality should be available in t…
No true scotsman and all that, but I suspect few documents in the wild are bare Latex.