The following issue has been updated:

    Updater: Dave Brondsema (mailto:[EMAIL PROTECTED])
       Date: Tue, 8 Mar 2005 9:37 PM
    Changes:
             environment changed to 
             Component changed to Plugin: OpenOffice.org
             Component changed from Other
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.cocoondev.org//browse/FOR-262?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-262

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

     Status: Reopened
   Priority: Major

    Project: Forrest
 Components: 
             Plugin: OpenOffice.org
   Fix Fors:
             0.6
   Versions:
             0.6

   Assignee: Ross Gardler
   Reporter: Charles Palmer

    Created: Sun, 22 Aug 2004 1:06 PM
    Updated: Tue, 8 Mar 2005 9:37 PM

Description:
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 

<!ATTLIST td
  %common.att; 
  %cell.span; 

Does this prevent cells from spanning rows and columns? 


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Reply via email to