[WIP]: BLD, MAINT: Configure MathJax v3 #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
As described in scipy/scipy#20518, I'm trying to update SciPy's internal/vendored MathJax submodule, which is coming from this repository on GitHub, to use MathJax v3.
It is to be noted that the MathJax project underwent a lot of changes through v2 and v3 because of a complete rewrite of the source code, which renders the Gruntfile no longer applicable for removing ancillary files, and possibly could be no longer valid since MathJax has undergone several quality-of-life changes and fixes. A migration guide is available, and I will be using this converter to convert from the older
MathJax.Hub.Config
entry point to the newer configuration block. It seems like it would be too much work to adapt the Gruntfile to work with v3 for MathJax, hence, a solution is to manually analyse needed files and copy them into this repository for being able to run MathJax. The converter is not fully compliant and does not work fully because of known issues, so, the rest of the configuration will have to be configured separately.Additional context
scipy/scipy#20518 (comment) describes the reasons towards implementing this (mostly security reasons in order to avoid CVEs that were discovered in v2.7.1 and v2.7.4; subsequently up to v2.7.9 and no longer present in v3).