|
I disagree that figures and tables are conceptually similar, but
sympathize with users who confuse similarly named attributes that
have subtly different meanings. It wasn't until I did my final
thorough review of the documentation that I realized we should
have used NOFLOAT instead of KEEP for figures. That would have,
at least, avoided the assumption that since figures can either
float or be kept that it must also be true that tables can either
float or be kept.
I'm not sure it is possible to float tables; I mean, I know that
it is impossible in V1.0 as implemented, but I'm not sure how
difficult a programming task it would be to float a table.
pa
|
| .1> I disagree that figures and tables are conceptually similar,
My claim of conceptual similarity is based on my use of figures and
tables as extensions to text. That is, when the narrative gets dense
or complex, it helps to draw a simple picture or include a table that
summarizes the facts. Most times it's not necessary for the figure or
table to be bound to the text. That's why floating is such a useful
layout concept.
While I was writing the preceding paragraph, I realized that it
probably wouldn't be long before I want to float an example. I checked
the User Manual and was pleased to find that <EXAMPLE_ATTRIBUTES>
includes a FLOAT argument.
.1> I'm not sure how difficult a programming task it would be to float
.1> a table.
Let's put floating tables on the wish list and trust the developers to
find a way to do it.
-- Ward
|