Erik Zachte wrote:
Of the remaining ones (if any), which are absolutely necessary
(meaning,
don't serve some doubtful decorative purpose;-) ?
I rather specify any option only once than on each cell.
As for doubtful decorative purpose: not quite NPOV ;) Colour helps to bring order to complex tables, CSS classes might do the trick, but will that be easier to apply than a <tr bgcolor=blue> ? (one needs to look up css definitions somewhere)
OK, so is there an example for * a row with several cells (say, more than 2) * that has some properties in common (e.g., background) * which can't be defined in the <table> / {| statement * in a table that is not one of a default type (countries, elements etc.) ?
I don't want CSS for *all* tables, just for the ones that occur over and again. Advantage: less to type, easier for newbies, settings can be changed with a central "switch" if desired.
Also, we were about to give <th> sone nice default background via CSS, right? That'll take care of many "colored row" problems, IMHO.
Don't get me wrong, it'll take ~5-10min to implement the <tr> thingy (probably less than writing all these mails;-) but what's the point?
|_ is too similar to |- and therefore hard to detect when editing the source, easy to confuse and mistype.
I am open to suggestions!
anything goes that is not confusing |= may be mistaken by unitiated as meaning <th> what about |+, |@ or |# ?
|# could be confused with the numbering wiki markup. |@ doesn't strike me as intuitive.
|+ is something I could well live with! :-)
Magnus