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 Fri, 08 Oct 2004 17:52:55 GMT
The following comment has been added to this issue:

     Author: Charles Palmer
    Created: Fri, 8 Oct 2004 12:52 PM
       Body:
I posted this as an issue on the OOo websitye and have just received this reply:

"Due to how headings are stored in the file format (OOo 1 + 1.1), the application doesn't
know about style/heading mapping if the styles are not used. So when the last use of the 'Heading
5' style is removed from the document (and a save/load cycle is done), the mapping is lost.

The OASIS format improves on this by explicitly assigning default outline levels to styles.
Hence I would think this problem should no longer occur in the new version.

dvo->es: I would consider this fixed for 2.0 (at least after CWS num0201 integration).
I'm not really in a mood to still change this in the old version. Please decide how to flag
this."

I don't know what they mean by "OASIS format" and "2.0" - presuambly there is a new OOo version
on the way. Warning though - this may mean different use of tags in content.xml, which may
require re-writes of openoffice-writer2forrest.xsl.
---------------------------------------------------------------------
View this comment:
  http://issues.cocoondev.org//browse/FOR-311?page=comments#action_11632

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

   Assignee: 
   Reporter: Charles Palmer

    Created: Wed, 6 Oct 2004 3:25 PM
    Updated: Fri, 8 Oct 2004 12:52 PM
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