> Ordinary markdowns have had /everything/ you mention for close to 20 years, except typesetting.

Huh? I roll to doubt. How do you do this stuff with markdown? I tried for ages but only got half-baked hacky "markdown extensions" which weren't even commonmark compliant. I've found nothing even remotely as powerful as typst in the markdown world.

▲

applicative 2 days ago | parent [-]

I don't know, since I haven't used a form not commonmark compliant since the spec came out. Get back to me when you want to get your typst file translated or in e-reader format.

▲

_flux 2 days ago | parent | next [-]

Typst html support is already available as an experimental feature, so e.g. EPUB probably isn't too much work in addition to that (as I understand it, it's basically zipped HTML with some metadata). It's also in the roadmap: https://typst.app/docs/roadmap/#:~:text=EPUB%20export .

If the translator has access to a service like typst.app, then I don't see too many obstacles for translating. But I don't have any experience on doing translations.

▲

applicative 14 hours ago | parent [-]

Why would I use a typesetting engine to output an epub or html? They are //by definition not typeset//, but the user e.g. increases font size and rewraps.

	▲	_flux 11 hours ago \| parent [-]
		Perhaps you would enjoy the rest of the tooling, that may be useful in scientific contexts or in books discussing programming languages. Or perhaps you would also want to publish in PDF, like for an actual print book. What kind of issues did you expect to encounter in translating Typst documents to other languages?

▲

josephg a day ago | parent | prev [-]

I’ve never seen a markdown based workflow which supports the features I listed. If I’m wrong, it would be easy to demonstrate it by citing some tools.

Just calling me a liar for disagreeing with you will convince nobody.

	▲	applicative 13 hours ago \| parent [-]
		> Like, being able to write scripts, have figures and custom styling, populate data from JSON files, plugins, typography, numbered sections, footnotes and all sorts of other stuff. Markdown doesn't even support comments properly! it is plain you want typst or latex and not a markdown or any other so called lightweight markup - and you were lying about footnotes, figures, numbered sections, and depending what you meant, a number of other things. It completely violates the concept that you are doing 'custom styling', typography ... you might as well add launching missiles, calling a C compiler, etc. Why not use microsoft word? I find markdowns irritating in many ways -- only those are not among them. Why would I want an intellectual document to be in a programming language?