This is all very old territory. As far as I know, NPAPI requires that the amount of space the equation takes up on a page be known in advance, rather than be calculated at run-time to be dependent on the MathML content. There is no support for baseline alignment of the equation with the surrounding text. The rendering can't adapt to the font and point size of the surrounding text, an absoluter requirement for math. There is no connection to accessibility. Authors are not interested in writing separate MathML files. With a typical technical paper containing hundreds of equations, it very quickly becomes a nightmare.
We in the MathML community fought with the Mozilla gods for a long time to get them to support MathML embedded in HTML but it was against their religion at the time. It is interesting to see some of these very same people adding it back in HTML 5, which will take 10 years to happen IMHO. MathML is not such a niche thing. It's inclusion in the DAISY ebook standard is enough to ensure its survival. The only thing stopping it being used in HTML is its lack of support in HTML in Firefox and it being totally missing in Firefox. The code to render both visually and aurally is available. It just needs the browser makers to support the right kind of glue (ie, plugin APIs). Paul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
