"Jacob S. Gordon" <jacob.as.gor...@gmail.com> writes: > I’m only referring to the user interface here, not internals (which I > don’t really have a strong opinion on). I interpreted “providing an > export backend” as something like my first message, where the user > needs to go through a derived backend separate from ox-html. Are you > talking about the implementation or interface?
I was mostly talking about internals. If you mean something like "Use `LaTeX' as an intermediary" in your first message, then it is _not_ what I had in mind. What I had in mind is some kind of internal backend that will be used by html/odt/etc. The advantage of using a backend is that we can plug export customization system - filters, custom templates, in-buffer options, etc. >> Emm. It should, I think. Via org-odt--translate-latex-fragments -> >> org-format-latex -> org-preview-latex-process-alist > > Certainly it’s wired up to do that, or dvipng and imagemagick wouldn’t > work, but there’s no way to use anything else. For example, try > exporting this to ODT: > > #+OPTIONS: tex:dvisvgm > \( a^2 + b^2 = c^2 \) > > Am I missing something? Well. There was no reason not to support dvisvgm. So, ox-odt now does support it. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=8b900ae37 -- 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>
