Skip to content
GitLab

Mathjax backlog · Changes

Page history
first round of edits. authored by Peter Krautzberger's avatar Peter Krautzberger
Show whitespace changes
Inline Side-by-side
Mathjax-backlog.md
View page @ 8ff68399
We collect potential features. This is not a discussion area but a presentation area for review.
We collect potential features. Note: This is not a discussion area but a presentation area for review.
* Completing the MathML implementation
* elementary math elements
* elementary math elements (mlongdiv, mstack etc) [spec](http://www.w3.org/Math/draft-spec/chapter3.html#presm.elementary)
* more mtable attributes (e.g., rowspan, colspan)
* in-table alignments
* right-to-left support
* improve annotation-xml
* use static image as preview
* improved ContentMathML support
* integrate David Carlisle's pure-JS update (no xslt)
* as part of that, modularize Content-to-Presentation generation
* Speed Improvements
* “tweaked” native MathML output that works around browser implementation deficiencies.
* improve our “tweaked” native MathML output that works around browser implementation deficiencies.
* “simple” HTML-output (faster but potentially lower quality)
* collaborating with browser developers to improve MathJax speed
* integrate jqmath as output option
* Caching APIs for local storage and mobile device storage
* investigating potentially faster output formats such as canvas, VML
* investigating new output formats such as canvas
* server-side preprocessing (TeX to MathML, MathML to SVG etc)
* collaborate with browser developers to improve MathJax speed
* Accessibility
* Make UI (MathJax Menu) more accessible
* fix UI on mobile
* finalize discovery-mode of the UI
* Use ShadowDOM to push rendering out into the Shadow and keep MathML (or other inputs) in the Light.
* Add APIs for accessibility tools (AT) to interact with MathJax rendering as if it was native MathML. This includes
* handing MathML over to AT
* enable user navigation
......@@ -26,7 +32,6 @@ We collect potential features. This is not a discussion area but a presentation
* compatibility with user style sheets
* speech-text extension.
* collaborating with other open source solutions from Benetech or Google ChromeVox
* make MathJax menu accessible
* embedding alternative source formats of math (TeX, MathML, OpenMath, computer algebra notation)
* Content Testing
* server side testing
......@@ -34,55 +39,47 @@ We collect potential features. This is not a discussion area but a presentation
* enable MathJax outside the DOM
* enable server-side pre-processing
* Internal Testing
* fuzz testing
* improve fuzz testing
* integrating MathJax testing into other testing environments
* Interface improvements
* UI on mobile devices
* UI improvements
* copy&paste (share mechanisms, microdata, rdf, shadow dom, web components)
* discoverability of math on the page
* menu extensions
* search menu (enabling math search engines such as symbolab, wolfram alpha, Springer LaTeX search etc)
* Input improvements
* Create jqmath input jax
* Improve asciimath input
* Improve asciimath to MathML converter
* Create asciimath to TeX converter
* Create MathJax-TeX-to-Content-MathML generator
* Additional font options
* Asana webfonts, Neo Euler webfonts, Latin Modern, DejaVu fonts
* allow font mixing
* Local support for ubiquitous commercial fonts
* Lucida Sans, Apple symbol fonts, Arial unicode
* allow font mixing
* crowdsource font-metric generation for local fonts
* allow font mixing
* Input extensions
* official third party extension repository
* integration of existing solutions
* integration of existing extensions
* XyJax (xypic), mathapedia (pstricks), computer algebra (e.g. Sage Cell), chemdoodle, kitware (chemistry)
* community outreach: TeX-macro extensions
* Documentation
* improve community involvement
* Building a collection of code samples
* document plugin using MathJax in other systems, e.g., CMS, LMS.
* Native browser MathML development in Gecko and WebKit
* Improving Gecko/Firefox to re-enable native MathML output.
* Engaging in WebKit development
* Outreach activities
* MathJax workshop / conference
* MathJax community meetups
* Math accessibility workshop (AIM)
* MathJax in education (web literacy, authoring, annotation)
* MathJax in authoring tool chains for research and publishing
* Native browser MathML development in Gecko and WebKit
* Develop a long term project that would allow for Gecko/Firefox and WebKit/Safari development.
## User stories
Collecting [user stories](https://en.wikipedia.org/wiki/User_story)).
### Localization
Authors and Readers want to use the MathJax user interface in their native language. MathJax currently uses a number of English language strings in its UI, namely the MathJax Menu and the various messages (processing, error etc). To support global use of MathJax, a full localization of the UI allows MathJax users to flexibly decide on the locale and allows translators to contribute easily and efficiently.
Authors want to specify the UI language depending on the language of their content. Authors want to load translations they supply themselves, just like configuration options in general.
Readers want to be able to set the UI to their language of choice. Readers want to be able to copy&paste math even if they don't understand the surrounding language.
### Using MathJax outside the DOM
Developers want to use MathJax outside the DOM for testing. MathJax depends on the DOM and parts of its functionality does not make sense outside the DOM. We want to enable MathJax outside the DOM to the extent possible and provide APIs for [servers-side javascript implementations](https://en.wikipedia.org/wiki/Comparison_of_server-side_JavaScript_solutions).
......@@ -115,4 +112,4 @@ Users want documentation for writing TeX input extensions.
### Speed related enhancements
Authors don't want to worry about very large equations locking up the browser while rendering. Simileraly, community driven content can't afford to have a page lock up because of "vandalism" with huge MathML equations. Compare: [#425], [#409]
\ No newline at end of file
Authors don't want to worry about very large equations locking up the browser while rendering. Similarly, community driven content can't afford to have a page lock up because of "vandalism" with huge MathML equations. Compare: [#425], [#409]
\ No newline at end of file