https://bugzilla.wikimedia.org/show_bug.cgi?id=51698
--- Comment #13 from Peter Krautzberger <[email protected]> --- (In reply to comment #12) Thanks, Gabriel! That's very helpful. > I'm also looking forward to learning more about LaTeXML vs. MathJax options. > No browser supports Content MathML currently. The question then is if it is > still useful to produce it for search while always rendering via Presentation > MathML and/or server-generated SVG. That's a good question. Especially, if Content MathML from TeX can be good enough (with "random" authoring instead of firm semantic guidelines). > Copy&pasting entire formulas should be possible as long as our data-mw > attribute on the outer wrapper node is preserved. That has the TeX source, > which can be used to re-render the contents from scratch. This will enable > copy&pasting of entire sections including formulas. That would be awesome. Subexpressions seems impossible right now -- but one day, with shadowdom and a lot of great heuristics it might just work... > Are there popular screen readers that handle math? I agree that MathML is > probably better in the longer term, but for current screen readers a speech > string could still be a useful fall-back. At least if that would not prevent > a plugin like math player from using the MathML instead. A static speech string is never a bad idea for legacy screen readers. There are only two math accessibility solutions, MathPlayer and ChromeVox. AFAIK a number of screen readers ship MathPlayer but I'm not an expert on screen readers. Since ChromeVox is mostly JavaScript (and open source), an obvious idea is to create a MathJax extension based on its technology. The thing is that accessibility is about more than aural rendering; in particular synchronized highlighting is extremely important for learning and other non-vision disabilities. That can't work with static strings. > I think nobody is suggesting to generate *only* SVG. I'm glad I misunderstood you :) > I'm not sure about the need for reflow in Wikipedia, as the limits of texvc > seem to have motivated authors to handle this manually in TeX. I seem to have a very different experience :( Anyway, right now PNGs are the only option on mobile (bug 45816). -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
