"Jacob S. Gordon" <jacob.as.gor...@gmail.com> writes: >> IMHO, providing an export backend sounds much cleaner (and more >> flexible). > > No argument there. My concern is that a separate export path is a > surprise to the user. IOW, I could adjust `org-html-with-latex' to get > MathJax or images for math, but I’d have to change how I export to use > MathML. It feels a bit inconsistent to me.
Not really. Org export uses specialized internal export backends in some scenarios. For example, see `org-export-toc-entry-backend'. > One thing I noticed is that `org-odt-with-latex' can’t use image > generation methods from `org-preview-latex-process-alist' like the > HTML counterpart. Markdown could also benefit from images and MathML > (e.g. a README on sourcehut). Emm. It should, I think. Via org-odt--translate-latex-fragments -> org-format-latex -> org-preview-latex-process-alist -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
