Hi Ian, Ian Laurenson wrote:
I am having difficulty understanding the rationale for the way that cells are named in Writer tables. I do understand the way that cells are named but I don't understand the rationale. In a similar way I don't understand why the next cell selected is dependent on the way that the cells were created rather than on the way the table looks. Lastly, to me, the concept of having rows consist of sub rows makes it difficult to merge cells across OOo's concept of a row.
it's one of our goals for the next versions to implement the "rowspan/colspan" table model for OOo Writer.
I am currently trying to write a macro that takes the current document and convert it into MediaWiki format. In MediaWiki a merged cell is represented by having rowspan=y and colspan=x for the cell in the top left corner of the spanned range. From the OOo API the only way that I can see to work out row spans is via the name of the cell and I am finding this difficult.
Maybe you should try to use the current html export as an intermediate step towards your MediaWiki format. The html export filter already contains some magic that maps our internal "nested rows" table format to a table with rowspans/colspans.
Hope this helps, Frank --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
