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, 22 Oct 2004 06:19:38 GMT
The following comment has been added to this issue:

     Author: Frédéric Glorieux
    Created: Fri, 22 Oct 2004 1:19 AM
       Body:
I'm working on thousands of OOo files, I never see that, and I'm unable to reproduce your
bug. Don't you think it depends on OOo version ?

But something sure is, your transformation don't handle correctly the automated styles.

Open an empty doc, write some words, new paragrape, select this paragraph and put in bold.


<office:document>
 <office:automatic-styles>
  <style:style style:name="P1" style:family="paragraph" style:parent-style-name="Standard">
   <style:properties fo:font-weight="bold" style:font-weight-asian="bold" style:font-weight-complex="bold"/>
  </style:style>
 </office:automatic-styles>
 <office:body>
  <text:p text:style-name="P1">Un petit test</text:p>
  <text:p text:style-name="P1"/>
  <text:p text:style-name="Standard"/>
 </office:body>
</office:document>

I got some code to handle that, it works but is really not nice.

Last tip, if you need to check a lot the generated oo xml, add you an export filter (only
export) with an identity xsl, and then File/export/choose your filter



---------------------------------------------------------------------
View this comment:
  http://issues.cocoondev.org//browse/FOR-311?page=comments#action_11671

---------------------------------------------------------------------
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: Fri, 22 Oct 2004 1:19 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