Re: table rows in a galley

> I'm trying to separate my idea of structure from my idea of content
> very strictly, so that the document itself contains only the data
> that goes into the report, and the look and arrangement of that
> data is entirely up to Lout.

It's easy to come to grief when trying to separate content and
format.  We're all told that this is a good thing to do, but we
are not told which is which, except in useless platitudes.

You seem to have the definition I prefer implicit in the above:
format is what is common to several documents or several parts
of one document; content is what differs from one to another.
Separating out the format then has a practical purpose:  it
makes those common parts uniform, and allows them to change
uniformly if a change in format is decided upon.

This definition has some awkward consequences, however.  If
there is just one table heading, then it is content; if the
same table heading occurs in several documents, or in several
places in one document, then it's format.  There are probably
plenty of people who would disagree with this.

Jeff

ps If you send a galley into a table cell, that table cell
will probably grab as much horizontal space as possible,
leaving almost nothing for neighbouring cells.  You can
get around this by making the table cells fixed width,
using either their width options or the @Wide symbol.
I'm still not convinced that it is a useful thing to do.