From: Robert Miner <RobertM@dessci.com>

Date: Tue, 18 May 2004 00:28:16 -0500

Message-Id: <200405180528.i4I5SGw00843@wisdom.geomtech.com>

To: steve.swanson@mackichan.com

Cc: www-math@w3.org

Date: Tue, 18 May 2004 00:28:16 -0500

Message-Id: <200405180528.i4I5SGw00843@wisdom.geomtech.com>

To: steve.swanson@mackichan.com

Cc: www-math@w3.org

Hi Steve, > Just a few gentle remarks. > > The presentation examples in the note use > class='MathML-Unit' > But there is no explanation of this value. > > The example in section 8 is a little funny. Why not mark it up as written > (i.e. as a bevelled fraction with fences)? I don't think anyone every responded to you on this. I think the idea of the MathML-Unit value was that it should have the same effect as setting mathvariant="normal". Of course in a CSS-aware MathML implementation, then you could accomplish the mathvariant="normal" part by actually setting up a CSS rule using the MathML-Unit class. But for cases where you don't have a CSS-aware MathML implementation, you probably want to put in the mathvariant explicitly. Even in those cases though, including the class="MathML-Unit' at least marks the construct as a unit. In any event, now that a Math Interest Group has been rechartered, we can republish this Note, with updates and errata. So if you have other thoughts on the matter, please post them. And I agree about section 8... --Robert ------------------------------------------------------------------ Dr. Robert Miner RobertM@dessci.com W3C Math Interest Group Co-Chair 651-223-2883 Design Science, Inc. "How Science Communicates" www.dessci.com ------------------------------------------------------------------Received on Tuesday, 18 May 2004 01:28:55 UTC

*
This archive was generated by hypermail 2.3.1
: Tuesday, 6 January 2015 21:27:35 UTC
*