typst VS typst-lsp

I am happily experimenting with Typst right now (https://typst.app/ ), which compiles much faster than LaTeX and with a syntax very similar to md, together with nice support for math, figures and advanced settings.

Check out [typest](https://typst.app/) if you're looking to write a book yourself.

[Hypermedia Systems book](https://hypermedia.systems/) was written with it.

This [issue](https://github.com/typst/typst/issues/4224) and others like it are dealbreakers for me. There are numerous related issues, but the developers are stubbornly sticking to their interpretation—using the older definition of leading from the days of metal type, rather than the more modern concept of line-spacing. No other software or modern typesetting system I know of uses this approach anymore. This is particularly frustrating since I work with a lot of multilingual text, including Arabic, and it's very difficult to align the baselines when setting text in more than one column.

- Long-form, print-friendly report generation, including data visualization, tables and images

[0] https://github.com/typst/typst

I somehow didn't know about https://github.com/typst/typst. This is a really cool project, going to dig in further.

At first glance, this seems particularly useful for scientific-style notebooks, which aren't our primary focus. If the demand is there though, I don't see why we couldn't integrate.

It's kinda early, but we're looking at collaborating with https://typst.app/ (a modern LaTeX alternative) on this. They already have some of the low-level PDF writing infrastructure in place, and are working on something higher-level that we're hoping to use.

(you could also look at using Typst directly if you're not tied to HTML)

I think that I need something in between. Recently, I was checking typst. It is quite impressive. But I am not sure if I need a better LaTeX.

I think the previous author is confused because if you google "Typst", you end up at https://typst.app, which seems to only advertise the web GUI and not the open-source CLI tool.

> Now, it’s certainly possible that one could develop a new, generative typesetting language that captures the virtues that I’ve discussed above and is free of TeX’s historical baggage.

Like [typst](https://github.com/typst/typst)?

I'm not sure what you're referring to because when justification is enabled Typst uses almost the same line breaking algorithm as TeX. [1]

One problem we had was over-eager hyphenation. We've addressed that recently. [2]

[1]: https://github.com/typst/typst/blob/9b001e21121ab7b5645aa36f...

Are you using the VSCode extension to render the pdf? If so I just filed an issue which may be the same problem you are facing. Have you tried using the command line interface instead? It should work with the CLI. https://github.com/nvarner/typst-lsp/issues/100

[Here](https://github.com/nvarner/typst-lsp) it is, if you haven't found it yet. It's still in early stages obviously, and I can't speak to the vscode extension. But I got the lsp working just fine in neovim.