Time passes regards MathML: Of the major web browsers, recent versions of Gecko browsers (e.g., Firefox and Camino)[5], WebKit browsers (e.g., Chrome and Safari) and the Opera web browser support MathML natively.
Opera, since version 9.5, supports MathML for CSS profile,[6][7] but is unable to position diacritical marks properly.[8] Prior to version 9.5 it required User JavaScript or custom stylesheets to emulate MathML support.[9] Internet Explorer does not support MathML natively. Support can be added by installing the MathPlayer plugin. WebKit-based browsers such as Chrome and Safari currently provide support for MathML[10] in their latest nightly builds[11][12]. The KHTML-based Konqueror currently does not provide support for MathML.[13] Doesn't seem like that much of a barrier any longer... --hsm On Fri, Sep 10, 2010 at 1:12 PM, Karl Winterling <[email protected]> wrote: > On 9/9/2010 8:31 PM, Eli Barzilay wrote: > >> MathJax is the best solution I've seen so far -- but it's kind of >> cheating... "If we can't get broad support for renering math, we'll >> do it ourselves." This makes the result much less appealing as proper >> support -- like relying on js (probably means that things break left >> an right if I want to view local file:// html pages), or like >> requiring me to upgrade a js library when they have a new version (or >> maybe I can use code from their site, but then I rely on their server >> to have my documents in working shape). >> > > I suppose we have to ``cheat'' now. All major browsers claim they will > prioritize support for HTML 5, but the quality of Math rendering is totally > different. You need to worry about complicated issues like supporting user > input and handling baselines and ``stretchy'' operators correctly. For > example, Firefox 3.6 correctly stretches integral signs in displayed > equations but not general ``big'' operators, which violates the W3C > standard. If browsers are really serious about non-toy math support, they > need to hire someone with expertise in complex typesetting algorithms. > Solving most of these problems correctly would involve low-level changes to > a browser's rendering engine, which are unlikely to happen given priorities > in browser implementation. > _________________________________________________ > For list-related administrative tasks: > http://lists.racket-lang.org/listinfo/users > _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/users
