well, if you're not nesting tables, then you could just do the same thing with {row} and {cell} - if they aren't paired up, don't parse the orphan. And if {table} isn't nested, then you'd never have nested {row}s or {cell}s.
Without nesting, though, colspan & rowspan couldn't be "faked" by just table/row/cell. But perhaps it'd work just to pass the 'problem' on to HTML - i.e put in the colspan rowspan info if the writingML user says so and leave it up to them to figure it out?
All Writing.Com images are copyrighted and may not be copied / modified in any way. All other brand names & trademarks are owned by their respective companies.
Generated in 0.13 seconds at 8:05am on Jul 09, 2025 via server WEBX1.