I don't think I saw Ian's original comment, Just Roger's reply? > What I would be proposing for HTML5 is just the following list of > elements: > > math, mrow, mfrac, msqrt, mroot, mstyle, merror, mpadded, mphantom, > mfenced, menclose, msub, msup, msubsup, munder, mover, munderover, > mmultiscripts, mtable, mlabeledtr, mtr, mtd, maction
You would beed to include the leaf elements (mi mn mo mtext) otherwise there'll be no characters in the mathml!, also mspace is pretty important. But a more general point I think it's dangerous for a spec to be profiled by _implementations_. The Math WG activity has just been restarted at W3C and if there is a need to profile MathMl to presentation MathML (or a subset thereof) please can it be done _there_ so that there is some chance that mathml authoring tools can be customised to have options to generate code to match any profiled spec. > I don't like mlabeledtr very much (I have already expressed my views > about it to folks of the MathML WG) Roger, I don't see anything searching for http://www.w3.org/Search/Mail/Public/search?type-index=www-math&index-type=t&keywords=mlabeledtr&search=Search I know you've talked to us at conferences etc, but we're all getting old and if comments aren't on the comment list, then they are likely to get forgotten over time. _Now_ would be a really good time to make such comments as we are in the process of finalising the requirements for what extar features should be in MathML3, and what if necessary, features should be deprecated. I don't remember specific discussions about an <mtr label="..."> I would guess there woul dbe some convern about the label being an attribute rather than an element restricting the possibilities, but implementation advice on difficulties on teh current schem woul dbe taken seriously.... Ian wrote about entities > Yeah... Do we really need those? Some of them seem reasonable to add, but > 2000 seems like too many for the mnemonic advantage to beat just using > Unicode codepoints... I'd say that it's probably not worth including only a few, it would just lead to confusion. The problem is that much mathml is generated using tools and those tools may use entities, and if they do that the user hasn't much control over which are used, and how to fix things to remove entities that are not supported in the browser. It would be better to just get the MathML authoring tools to use characters or character refs directly and tell the user mathml entities are not supported (but html ones are) David _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
