forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [JIRA] Commented: (FOR-262) openoffice2forrest: add support for merged cells in tables
Date Sun, 05 Sep 2004 22:12:33 GMT
The following comment has been added to this issue:

     Author: Charles Palmer
    Created: Sun, 5 Sep 2004 5:12 PM
Hmmm. JIRA doesn't seem to deal very well with uploading files (or else I can't drive it).
The files listed in JIRA are not in the order I uploaded them, and the comments I added are
not evident. To remove confusion:

1 My sample OOo file which includes tables with merged cells is called TRM_Skeleton_Chapter.sxw.

2 I ended up uploading all of the modified openoffice-writer2forrest.xsl - changes are around
line 188. 

3 The xml file that saxon generates from the first two (a plausible treatment of the merged
cells) is called forrestdoc.xml. 

4 The HTML that Forrest generates from 3 (a pretty good start) is called forrestdoc.html 

5 the HTML that Forrest generates if it does all the processing itself (a mess!) is called

View this comment:

View the issue:

Here is an overview of the issue:
        Key: FOR-262
    Summary: openoffice2forrest: add support for merged cells in tables
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Forrest

   Reporter: Charles Palmer

    Created: Sun, 22 Aug 2004 1:06 PM
    Updated: Sun, 5 Sep 2004 5:12 PM

Processing of OpenOffice files is useful, but tables containing merged cells are not handled
properly, preventing the use of many OpenOffice documents with Forrest.

If you merge two cells in OOo you get this attribute: table:number-columns-spanned="2" and
this could translate into the HTML colspan="2" attribute. But it's not happening - does this
first require an enhancement of the Forrest DTD? Which seems to contain the following:

<!ENTITY % cell.span 'colspan CDATA "1"
         rowspan CDATA "1"'> and 


Does this prevent cells from spanning rows and columns? 

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