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?