[uf-new] an equation/MathML/TeX microformat?
james at howison.name
Sat Oct 27 10:46:46 PDT 2007
Since you are focusing on image files always being present ("Equation
images are 100% reliable") would another option be to encode the
MathML or TeX into the image file, then use a class name to indicate
that this image should be parsed to look for the data.
eg stick it into the Description or Comment field (or make your own
field keyword) in a PNG file:
That could be added to some of the commonly used MathML->PNG or TeX-
>PNG tools. eg
Then you could use something like:
<img class="parse-image-for-mathml" alt="natural language description
of forumla" src="image-with-embedded-MathML.png" />
Of course this would need a tool to read the text out from the image
file, but those are widely available. Client side applications that
supported MathML could even read the MathML out of the image and
replace the PNG with the preferred MathML content.
Yeah, it wouldn't be in the HTML file, but you'd almost always also
have to download the image representation, no?
It would have the advantage of being able to be easily emailed too :)
On Oct 27, 2007, at 11:46 AM, Paul Topping wrote:
> For an explanation of why I'm looking to embed MathML and/or TeX in
> HTML, I refer you to my original post for the details. The short
> is that MathML is not a universal enough solution. I am aware of
> most of
> what you mention below (especially the stuff about my own company's
> products -- thanks!) and agree with it. Perhaps I should come at this
> from a slightly different angle.
> Instead of addressing the successes and failures of MathML, let's look
> at the many "solutions" to the equation display in a web page problem.
> There are many websites that represent equations as images. They do
> because of the universal browser compatibility of HTML with equation
> images. MathML is not a solution as it is not close to being
> supported in browsers. This is a big issue in education which is
> not in a position to dictate browsers and, perhaps more importantly,
> doesn't want to embrace any solution that might require the user to
> download plugins and/or fonts. Equation images are 100% reliable.
> Pretty much all the equation images are produced by rendering TeX or
> MathML using a variety of tools. In the case of TeX at least, this
> textual representation is also potentially useful in the browser so
> math websites embed the TeX in alt text or as a comment. Many don't
> expose this textual representation at all.
> If math websites embedded the TeX or MathML used to produce each
> equation image in a standardized manner, it would enable client-side
> software to provide math accessibility and interoperability. And,
> if it
> could be done in a way that didn't interfere with other HTML features,
> such as commandeering alt text away from its intended purpose, that
> would be a win. Finally, it needs to be done in a rigorous way. For
> example, if a certain version of LaTeX is used for the representation,
> that should be declared so the s/w that processes the notation should
> not have to sniff and guess.
> Paul Topping
> Design Science, Inc.
>> -----Original Message-----
>> From: microformats-new-bounces at microformats.org [mailto:microformats-
>> new-bounces at microformats.org] On Behalf Of Benjamin Hawkes-Lewis
>> Sent: Saturday, October 27, 2007 6:25 AM
>> To: For discussion of new microformats.
>> Subject: RE: [uf-new] an equation/MathML/TeX microformat?
>> On Thu, 2007-10-25 at 15:39 -0700, Paul Topping wrote:
>>> I'm aware of the effort to support MathML in HTML5 but this effort
>>> unlikely to bear fruit. Besides, I'm looking to create something
>>> will work in "plain old HTML" which, as I understand it, is part of
>>> microformat philosophy. As I stated, MathML was originally intended
>>> be implemented in browsers but the actuality leaves something to be
>>> desired. With HTML5, I would simply be waiting for yet another thing
>>> be implemented in browsers. Exactly what I want to avoid.
>> Personally, I believe wanting to use MathML is one of the rare
>> use-cases that justifies choosing XHTML over HTML 4.01, in which case
>> you can inline MathML directly into your markup.
>> Can you provide some more details about the problem you're trying to
>> solve, in particular:
>> 1. What are the deficiencies of existing techniques for using
>> mathematical markup in conjunction with HTML that you are
>> expecting to overcome?
>> 2. What are the key existing consuming agents you'd like the solution
>> those deficiencies to work with? e.g. What platforms, browsers, and
>> assistive technology?
>> Currently, your company's MathPlayer ActiveX plugin can already speak
>> maths and has MSAA support for assistive technology:
>> Gecko has built-in support for a subset of MathML; the FireVox
>> turns Firefox into a self-voicing browser on all three major
>> and can read MathML using Abraham Nemeth's Mathspeak rules:
>> The next version of Opera will include support for a subset of MathML
>> and restore (some level of) support for assistive technologies on
>> Windows and Mac:
>> The only major engine missing support for MathML at all is WebKit:
>> This situation could be a /lot/ better.
>> Your problem seems very similar to the problem of inlining RDF in
>> The suggested approach of dumping XML markup inside comments was
>> actually used by Creative Commons and Moveable Type's Trackback
>> But I can't really see how embedding MathML markup inside HTML
>> is supposed to improve things with existing (or even future)
>> agents. You did say this:
>>> Also, I want to put the MathML or TeX in the page, not in separate
>>> documents. Typical pages with math in them might have dozens of
>>> equations. Having their representation in separate files is
>>> inefficient but perhaps the biggest problem is that it makes
>>> a lot more tedious as lots of small files have to be managed.
>> The web stack tends to work by stitching together lots of different
>> resources to make up the final presentation the user experiences when
>> she visits a URI: multiple HTML documents, scripts, stylesheets,
>> Flash movies, and so on all get bound together by a master document.
>> generally sceptical about attempts to fight against this model in the
>> name of efficiency without changing the HTML specification itself.
>> There's also an issue of efficiency for consuming agents that don't
>> support MathML and would have to waste bandwidth on MathML
>> embedded in
>> Having said that, additional requests are more expensive than
>> bytes. But even if you have to externalize MathML outside the main
>> document, you could (I guess) cut down the additional requests to
>> one by using fragment identifiers to pinpoint individual equations in
>> XML document containing a series of equations. You could even make
>> referenced document an XHTML version of the HTML document, and use a
>> <link rel="alternate" type="application/xhtml+xml"> element to point
>> the XHTML version from the HEAD of the HTML version, and use the HTML
>> HREF and LONGDESC attributes to point to fragment identifiers for
>> particular equations. HTTP content negotiation could perhaps be used
>> send supporting consuming agents to the XHTML version in the first
>> For very short equations, you might be able to do away with the
>> document altogether by using data URIs instead of referencing an
>> external document:
>> If authoring tools make creating master documents hard, I think that
>> highlights a flaw in the authoring tools in question, and the
>> tools are likely to be a little easier to "fix" than consuming
>> OpenDocuments consist of an archive of multiple resources, but the
>> experience of editing an OpenDocument in OpenOffice.org is of editing
>> seamless document.
>> Using HTML comments to hide stuff is generally a bad idea since
>> should be disposable and sometimes are discarded. There are cases
>> that doesn't matter. For example, it doesn't matter when conditional
>> comments are used to serve different styles to IE are okay
>> because, if
>> content has been kept separate from presentation, it should be
>> to use the browser's default CSS to achieve a usable presentation of
>> document. Now there could be cases where using comments is worth the
>> risk even for data that is important to understanding a document, but
>> don't really see sufficient advantages in this particular case to
>> the costs.
>> Benjamin Hawkes-Lewis
>> microformats-new mailing list
>> microformats-new at microformats.org
> microformats-new mailing list
> microformats-new at microformats.org
More information about the microformats-new