Rudolf Adamkovič <salu...@me.com> writes: >> Are these extensions no longer supported? > > MathJax 3+ supports extensions, and one can load them in multiple ways. > See [1]. It deserves some thinking, for the extensions mirror LaTeX > extensions. So, to make both HTML and PDF work, one has: > > Use the Physics package in both LaTeX and MathJax. > > #+latex_header: \usepackage{physics} > > #+html_head_extra: <div style="display: none"> > #+html_head_extra: \( > #+html_head_extra: \require{physics} > #+html_head_extra: \) > #+html_head_extra: </div> > > (The example taken from my Org notebook.) > > [1]: https://docs.mathjax.org/en/latest/input/tex/extensions.html > > That said, I do not currently have bandwidth to extend the scope of the > patch to include MathJax extensions. (Note that they have never worked > anyway, so the user loses nothing, and we correct documentation.)
Then, please mention this in the NEWS. Something like "we drop extension support as it never worked anyway". > A slight digression, just FYI: > > I realized that I should have improved LaTeX to SVG exports instead of > focusing on MathJax. Org supports LaTeX environments, but outside of > PDFs, it does so poorly. Packages such as TikZ, for example, do not > work out of the box, so people use Babel to hack around it. Worse > still, Org does not even properly adjust baselines for inline math, so > HTML exports remain barely usable for any mathematical work. > > If we fix LaTeX, Org could have fast and good mathematics, with no > JavaScript, like Wikipedia has. Then, we could use it by default, > instead of MathJax. > > Having good support for LaTeX would position Org as the king of markup > editors, because LaTeX can do everything under the sun. For instance, > one can typeset a chess game in a couple of lines. Or sheet music. Or > molecules in three dimensions. No mainstream Markdown editor or web > authoring tool can do that. Yet, Org can *almost* do it. Patches are always welcome ;) > + (append `((,(if (plist-member options 'autonumber) > + 'tags 'autonumber) > + nil) > + (,(if (plist-member options 'linebreaks) > + 'overflow 'linebreaks) > + nil)) > + options))) You may even drop append and use ,@options inside `(...). Not a big deal though. > + (`scale > + (when (stringp value) > + (setq value (string-to-number value))) > + (when (>= value 10) If value is invalid string (not an actual number), `string-to-number' will return 0. This may cause very strange export output I think. -- Ihor Radchenko // yantar92, Org mode contributor, 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>