On Thu, Jan 15, 2015 at 6:11 PM, Raniere Silva <raniere-Xhq86aZylhT3fQ9qLvQP4Q@public.gmane.orgmp.br> wrote:

MathML rendering tools isn't as good as LaTeX. Firefox/Gecko has the best
implementation so far. "Community WebKit" (e.g. used by [Epiphany]) and
"Apple Webkit" (e.g. used by Safari) have some basic support to MathML
but Chromium/Chrome don't have neither Internet Explorer.

I would like to add that even Firefox/Gecko having one of the best support for MathML around -- it is still not enough! Under certain situations even if you feed MathJax certain MathML code it will revert back to HTML+CSS depending on the Firefox version of the user... because it know the shortcomings of the browser.

Frédéric Wang has worked intensively in fixing the MathML display bugs in Gecko and WebKit, and when the masters fold his code in -- we will have a nicer MathML level display in HTML engines. Anyone interested should check his blog:

http://www.maths-informatique-jeux.com/blog/frederic/

Most of the EPUB readers that support MathML use Gecko as rendering engine or
MathJax that requires Javascript enabled.

And the ones that don't are almost all using Adobe Digital Editions for rendering engine - one of the worst out there! I am writing a paper "On determining the HTML rendering engine of ePub readers" (based on what they do wrong with CSS) and this was a big surprise for me. It looks like things are changing and Kobo started to move away from ADE, but overall the industry is moving very slowly.

> However, I recently figured out that
> ePub seems to support SVG as well and it is actually possible to turn LaTeX
> into SVG output (see e.g. http://dvisvg.sourceforge.net/ and
> http://svgkit.sourceforge.net/SVGLaTeX.html).

That's true. Wikipedia does it.

The caveat being ... the support of SVG in browsers is roughly two years ahead of support of SVG in ePub readers.

Paulo Ney