Hey Ihor, I think we might be talking about different levels on both points.
On 2025-08-09 11:27, Ihor Radchenko wrote: > Not really. Org export uses specialized internal export backends in > some scenarios. For example, see `org-export-toc-entry-backend'. On 2025-07-13 09:57, Ihor Radchenko wrote: > IMHO, providing an export backend sounds much cleaner (and more > flexible). 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? > 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? Thanks, -- Jacob S. Gordon jacob.as.gor...@gmail.com Please avoid sending me HTML emails and MS Office documents. https://useplaintext.email/#etiquette
