- From: William F Hammond <hammond@csc.albany.edu>
- Date: Sat, 29 Mar 2008 16:59:29 -0400
- To: Ian Hickson <ian@hixie.ch>
- Cc: www-math@w3.org
Ian Hickson <ian@hixie.ch> writes:
> Cool, that's very encouraging. Any knowledge you have about that would be
> great. Is there any documentation on common MathML errors? Is there any
> documentation on what elements could be implied?
Such knowledge is applicable in-house on the server side.
> Is there any reason digits couldn't imply <mn>, for example, and
> punctuation couldn't imply <mo>? Any help here would be greatly
> appreciated.
None except the demise of the March 1995 draft of HTML 3.0.
> MathML is a very big language, with just shy of 190 unique elements in
> MathML2 (HTML4, including all the deprecated elements, has but 91). Could
> we get away with making that simpler for HTML, e.g. by not including
> support for Content markup in the text/html variant?
For html5 just include presentation MathML elements (not very many in total).
> One of the use cases is the mixing of graphics and form controls into
> equations. Is it possible to extend MathML to allow specific HTML5
> phrasing-level elements (like <em>, <img>, <input>, also maybe the <svg>
> element) wherever the <mglyph> element is currently allowed, or something
> along those lines?
Not anywhere <mglyph> is allowed, but maybe a small number of these
inside <mtext> where the recursive content is presumably ignored
under pasting into computer algebra systems.
-- Bill
Received on Saturday, 29 March 2008 21:00:09 UTC