forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iss...@cocoondev.org
Subject [JIRA] Commented: (FOR-311) OOo Headings bug causes Forrest to fail
Date Thu, 21 Oct 2004 15:47:38 GMT
The following comment has been added to this issue:

     Author: Clay Leeds
    Created: Thu, 21 Oct 2004 10:47 AM
       Body:
I recently added three files:

1. openoffice-writer.sxw - 9 kb
    An openoffice-writer.sxw file I was hoping to submit as a
    "patch" for forrest's seemingly flawed openoffice-writer.sxw file.
    My version includes a modified style.xml including Heading 3,
    Heading 4, and Heading 5, as well as a content.xml file which
    includes examples of these styles. The Forrest version is missing
    examples of Heading 3, Heading 4, & Heading 5, so the styles
    are not retained due to the bug.

2. openoffice-writer2forrest.xsl - 12 kb
    An improved openoffice-writer2forrest.xsl stylesheet which
    attempts to work around the bug by also formatting improperly
    structured OOo Headings. My version needs help, as it doesn't
    cycle through Headings (it only accounts for Heading 1-5). It
    would be better to use XSL to cycle through '"Heading "+n' or
    something.

3. openoffice-writer_clay.diff - 0.2 kb
    A diff of my openoffice-writer2forrest.xsl to the version in the
    forrest distribution.
---------------------------------------------------------------------
View this comment:
  http://issues.cocoondev.org//browse/FOR-311?page=comments#action_11670

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-311
    Summary: OOo Headings bug causes Forrest to fail
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Forrest
 Components: 
             Other
   Versions:
             0.6

   Assignee: 
   Reporter: Charles Palmer

    Created: Wed, 6 Oct 2004 3:25 PM
    Updated: Thu, 21 Oct 2004 10:47 AM
Environment: All

Description:
There appears to be a bug or feature in OpenOffice which affects how haedings are stored as
XML. It appears that if a virgin document is opened then all headings are stored in <text:h>
tags, but if an existing document is opened that lacks a particular haeding style, then if
you create that heading style it is stored in <text:p> tags.

This causes Forrest to mis-interpret headings, as the Forrest OOo XSL file identifies OOo
headings by looking for the <text:h> tags.

You can reproduce this effect as follows:
 
1	Create a new text file.
2	Create 20 lines of text, one of each style Heading 1-10, with a "default" format line between
each.
3	Save this file (as "head.sxw" for example), unzip it and examine its content.xml. You will
see that all of the headings are of the format:

 <text:h text:style-name="Heading 5" text:level="5">Heading 5</text:h>

4	Copy head.sxw this to headless.sxw.
5	Open headless.sxw, delete the Heading 5 line, then save and close the file.
6	Reopen headless.sxw, and add a new line where the original Heading 5 line had been. Change
the style of this new line to Heading 5. 
7	Save this file, unzip it and examine its content.xml. The new line of style heading 5 is:

  <text:p text:style-name="Heading 5">New heading 5</text:p>


So ...

So perhaps openoffice-writer2forrest.xsl should reconsider how it matches headings. Instead
of the current:

  <xsl:template match="text:h[@text:level='1']">

maybe it should match text:h or text:p with an attribute text:style-name="Heading 1" etc.

(Hopefully I will work out how to attach the .sxw and .xml files so you can see these examples
easily)


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


Mime
View raw message