On Wed, 27 Sep 2006, William F Hammond wrote:
> 
> 1. There's the old issue, related to dual parsers, of trying to get 
> Mozilla family user agents to give proper handling of XHTML+MathML when 
> served through text/html -- following early Amaya practice.  (In the end 
> the W3C HTML WG refused to support this idea and spawned the mimetype 
> application/xhtml+xml.)  It seems that formally correct XHTML+MathML 
> would now gain coverage as text/html under current WhatWG thinking, at 
> least when XML namespaces are evident only through use of the xmlns 
> attribute (which would be ignored in tag soup), i.e., no use of xml 
> namespace prefixing.  Is this correct?

I'm confused by your terminology.

MathML using namespaces and XML syntax would not, under the WHATWG 
proposals here, be formally correct. XML sent as text/html is never 
correct per the "WHATWG thinking".

What is being proposed here is a non-XML syntax, to be formally described 
in the HTML5 specification, which, went processed by an HTML5 UA, would 
generate a DOM that can then be processed per the MathML2 specification.

Per the WHATWG specifications, the presence of an "xmlns" attribute is 
always a conformance error in any content sent as text/html.


> 2. Is WhatWG entertaining the idea that off-the-cuff tag soup writers 
> will generate MathML content that's good enough for Mozilla rendering?

The idea being entertained is that off-the-cuff HTML5 authors, and HTML5 
editors, would create content which, when processed by an HTML5 UA (such 
as Mozilla, in due course), would render as MathML markup would.


> The W3C Math group has announced that it is beginning to think seriously 
> about author-level markup for math.
> 
> Long term -- say ten years in the future (we've already been at this for 
> ten years) -- I think author level math additions to the tag soup 
> vocabulary would work out much better, especially with enhanced CSS 
> support.

On the very short term, the proposal here is just a proof of concept. On 
the medium term (12 months) I was considering specifying more complex 
parsing rules for MathML such that the same MathML2-compatible DOM could 
be obtained from much smaller markup, e.g. by implying <mo> tags around 
operators and <mn> tags around numbers.

HTH,
-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
_______________________________________________
dev-tech-layout mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-layout

Reply via email to