[josephg]

> you have literally just made something up.

Huh?

I’ve authored a couple academic articles in typst. At its base, typst is very similar to markdown. You use == for section headers, * for italics and so on. I authored articles in typst just as I would in markdown. Then I do another pass later filling in tables and figures, editing and doing typesetting.

It works great. Maybe not for your needs, but it works great for mine. And I’m keen to try the new html support in typst for blog posts.

[applicative]

Except what you made up was something about markdown and latex, if you look, not something about typst. I gathered you know typst and said not a thing about your cognitions specific to it.

I wish you luck with e.g. automated translation and editing of your typst documents, and look forward to the compile fails when you use 'html support' on these translated files. There are many curiosa with the markdowns but also very very very deep reasons for the uptake, which is only increasing with the AIs.

[josephg]

No, latex does not resemble markdown while authoring. Text ends up intermingled with ugly \sectionheader tags everywhere.

Re: automated translation, you’re projecting your requirements onto me. I can see how automatic translation would be difficult with typst. But, I don’t translate my blog into multiple languages. So that doesn’t matter to me. What does matter is the requirements I listed above - like numbered figures, captions on my images, programmatically generated tables, footnotes and so on.

You repeatedly claimed you can do this stuff with markdown. I don’t believe you.