From: Ihor Radchenko <firstname.lastname@example.org>
Subject: [ANN] Dropping MathJax 2 support in Org 9.6
Date: Mon, 21 Nov 2022 02:49:49 +0000 [thread overview]
Message-ID: <87o7t1ja2a.fsf@localhost> (raw)
We are moving away from the outdated MathJax 2 to MathJax 3 in Org export.
This change is a breaking change as MathJax 2 is not compatible with
We have done all we could to not break the existing usage. However, some
users might still be affected. In particular, people who customized
`org-html-mathjax-options' to point to a custom MathJax 'path to MathJax
2 will experience breakage. Other users, including people who customized
other MathJax options (not 'path), will _not_ be affected as Org will
auto-convert MathJax 2 style options to MathJax 3.
See more context and the discussion in
Below is the relevant ORG-NEWS entry:
Org now uses MathJax 3 by default instead of MathJax 2. During HTML
exports, Org automatically converts all legacy MathJax 2 options to
the corresponding MathJax 3+ options, except for the ~path~ option in
which now /must/ point to a file containing MathJax version 3 or
later. The new Org does /not/ work with the legacy MathJax 2.
Further, if you need to use a non-default ~font~ or ~linebreaks~ (now
~overflow~), then the ~path~ must point to MathJax 3 or later.
See the updated ~org-html-mathjax-options~ for more details.
MathJax 3, a ground-up rewrite of MathJax 2 came out in 2019. The new
version brings modularity, better and faster rendering, improved LaTeX
support, and more.
For more information about new features, see:
MathJax 3 comes with useful extensions. For instance, you can typeset
calculus with the ~physics~ extension or chemistry with the ~mhchem~
extension, like in LaTeX.
Note that the Org manual does not discuss loading of MathJax
extensions via ~+HTML_MATHJAX~ anymore. It has never worked anyway.
To actually load extensions, consult the official documentation:
network (CDN) provider from CloudFlare to jsDelivr. You can find the
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>
reply other threads:[~2022-11-21 2:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).