Hi Don,
If your tables were to obey the CALS table specification things would be simpler and you would require less customization work.
The CSS changes I proposed to define the cells, rows, tables and table groups are the first stage in getting the rendering to work.
Afterwards if your table has column widths, cell and row spans you need two things:
1) Have the cells that span multiple rows or columns properly rendered. Oxygen does this with Java extensions implemented at framework level.
If your tables look like HTML tables, DocBook tables (which obey the CALS table specification) or TEI XML tables, Oxygen should handle this without the need for you to implement the column span provider in Java.
So for example if you have this XML:
Code: Select all
<root>
<table rows="3" cols="2">
<head>title</head>
<row role="label">
<cell cols="2">a</cell>
</row>
<row>
<cell rows="2">b</cell>
<cell>c</cell>
</row>
<row>
<cell>d</cell>
</row>
</table>
</root>
and this CSS:
Code: Select all
root, head {
display:block;
}
table {
display: table;
}
row {
display:table-row;
}
cell {
display:table-cell;
border:1px solid black;
}
Oxygen will properly display the cells spanning horizontally and vertically because the table adheres to the TEI XML standard.
If your table uses other attributes rather than "cols" and "rows" to define spans, then you will need to implement some Java extensions to tell Oxygen the necessary information to display the table.
Have you implemented a custom "Document type association" framework configuration in the Oxygen Preferences->"Document Type Association" page? Such a framework extension can contribute Java extensions to control table rendering.
https://www.oxygenxml.com/doc/versions/ ... ement.html
2) Create custom Author actions to insert columns, rows, join and split cells, this older blog post discusses how to implement Author actions similar to what our DocBook XML editing offers:
https://blog.oxygenxml.com/topics/addin ... ework.html
Regards,
Radu