From: Frédéric WANG <fred.wang@free.fr>

Date: Thu, 24 Sep 2009 22:42:48 +0200

Message-ID: <4ABBD9C8.6010201@free.fr>

To: "www-math@w3.org" <www-math@w3.org>

Date: Thu, 24 Sep 2009 22:42:48 +0200

Message-ID: <4ABBD9C8.6010201@free.fr>

To: "www-math@w3.org" <www-math@w3.org>

In section 3.2.5.8 "Stretching of operators, fences and accents", it is written that an operator should be stretched in each possible direction: "There is no provision in MathML for specifying in which direction (horizontal or vertical) to stretch a specific character or operator; rather, when stretchy="true" it should be stretched in each direction for which stretching is possible. It is up to the renderer to know in which directions it is able to stretch each character." Currently, it seems that the stretching directions that one would expect for an operator are only determined by the technical constraints imposed to the renderer. Nevertheless, this overlooks the fact that renderer could use techniques to make possible stretching in both direction, for any single character. For instance, some graphics library allow "scale transform" (as defined in chapter 7 of SVG rec) that can be used for this purpose. In that case, some weird stretching could happen such that a vertical arrows stretched horizontally. Hence I suggest to add a notion of "natural" direction that will be used when an operator needs to be stretched (with either a default or explicit stretchy=true). For instance the working draft already suggests "vertical" direction for most fences, "horizontal" direction for some accents, and both directions for diagonal arrows. Apart from the examples given in the working draft, it would of course be up to the renderer to determine what direction is "natural" for a given operator. For example, an integral symbol is likely to be defined as "naturally" vertical.Received on Thursday, 24 September 2009 20:41:33 GMT

*
This archive was generated by hypermail 2.2.0+W3C-0.50
: Saturday, 20 February 2010 06:13:05 GMT
*