From: Dave P. <dav...@gm...> - 2016-03-23 17:00:55
|
On 23 March 2016 at 16:50, Maurice van der Pot <gri...@kf...> wrote: > On Wed, Mar 23, 2016 at 07:26:33AM +0000, Dave Pawson wrote: >> > It might be, but I consider rowspan/colspan to be a content decision and >> > not a styling one. >> >> I disagree. Presentation - spanning, is not, IMHO, content. > > Ok, then I'm not sure how you would separate the content from spanning. > Would you always create all cells in the content and merge them in > presentation? The content (my view) is within the cells, not how the cell content is shown. > > What would you expect to find in the content for a table that has a row > of which the first cell should span 2 columns? As today |content|| then some 'identity' for that row (table[@id='table1']/tr[3]/td[1] ) then some styling information, e.g. 'span=2' which enables the presentational aspect to be specified external to the content? > > And similarly, what would you expect in the content for a table that has > a cell in the first column that (when presented) should span 2 rows? The same mechanism will work. For example table[@id='table1']/tr[3]/td[1], rowspan=2 with no change to MD syntax? HTH -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. http://www.dpawson.co.uk |