W3C home > Mailing lists > Public > www-math@w3.org > August 2010

Re: Why mtable doesn't have also an attribute height

From: Urs Holzer <urs@andonyar.com>
Date: Wed, 18 Aug 2010 20:14:11 +0200
To: Neil Soiffer <NeilS@dessci.com>
Cc: Ionel Alexandru <ionel.alexandru@gmail.com>, www-math@w3.org
Message-Id: <201008182014.11497.urs@andonyar.com>
Allow me to join this discussion.

Neil Soiffer wrote:
> For the use cases of tables in math, each cell is laid out
> horizontal, line wrapping contents if needed because of a width
> restriction.  The cells, and ultimately the table, will then have a
> height that is computed based on the width of each cell. 
> Restricting a table to a page or column width is common in laying
> out tables.  A height restriction would imply that widths are not
> constrained so that the height restriction can be met.  Of the to of
> my head, I think it would be difficult to implement since multiple
> widths would need to be tried.
> I am unaware of a use case for restricting or setting an explicit
> height. Do you have a use case in mind?

Simple commutative diagrams could be built using tables. To make them 
look better one could adjust the height of certain rows as well as the 
width of certain columns. This would work good because a stretchy 
operator (for example an arrow) stretches to the size of the mtd if it 
is it is the sole subexpression of the mtd.

Is there another way to achieve the same in MathML? Anyway, for 
commutative diagrams, one perhaps better uses SVG (or even better, 
MathML in SVG).

Received on Wednesday, 18 August 2010 18:14:45 UTC

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