forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [JIRA] Updated: (FOR-312) Merged cells in OOo tables
Date Fri, 05 Nov 2004 15:42:38 GMT
The following issue has been updated:

    Updater: David Crossley (
       Date: Fri, 5 Nov 2004 9:41 AM
             Component changed to Plugin:
             Component changed from Other
For a full history of the issue, see:

View the issue:

Here is an overview of the issue:
        Key: FOR-312
    Summary: Merged cells in OOo tables
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Forrest

   Reporter: Charles Palmer

    Created: Wed, 6 Oct 2004 3:48 PM
    Updated: Fri, 5 Nov 2004 9:41 AM
Environment: All

The current state-of-the-art is that Forrest supports OpenOffice Writer tables with horizontally
merged table cells, but not vertically merged cells. Issue FOR-262 made some improvement but
did not finish the job.

The issue seems to be that OOo deals with cells merged vertically by creating sub tables to
the left or right of the merged cells, rather than some equivalent of the HTML rowspan attribute.

I have hacked openoffice-writer2forrest.xsl, and dealt with this by identifying the sub-table
element in the xsl file and creating a new HTML (or Forrest) <table> whenever I find

This seems to work OK, but when rendered as HTML the borders of the cells are too thick -
maybe we are getting two sets of table borders. This needs some further investigation - there
should be some HTML table border attributes that can resolve this. For example, there seems
to be an HTML construction <table frame="void"> which could possibly do the job, but
just adding this into the openoffice-writer2forrest.xsl file did not work. Maybe giving the
sub-table a class= or id= attribute could allow appropriate processing down-stream, maybe
within a skin CSS, or maybe we need to be able to pass through more HTML.

I will add files to this issue - a hacked openoffice-writer2forrest.xsl (which no doubt needs
polishing!) and a tables.sxw file that contains example tables and further documentation of
this issue. (Sorry I am not enough of a software person to finish the fixes).

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message