The following issue has been updated:

    Updater: Florian G. Haas (mailto:[EMAIL PROTECTED])
       Date: Fri, 4 Feb 2005 4:15 PM
    Comment:
Patch that fixes the 3 issues listed under "in particular" in the original 
comment.
    Changes:
             Attachment changed to openoffice.org-plugin.20050204.patch
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-433
    Summary: OpenOffice.org plugin produces invalid intermediate documents
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Forrest
 Components: 
             Plugin: OpenOffice.org
   Versions:
             HEAD

   Assignee: 
   Reporter: Florian G. Haas

    Created: Fri, 4 Feb 2005 4:06 PM
    Updated: Fri, 4 Feb 2005 4:15 PM
Environment: Tested on Debian Sarge with Linux 2.4.27 an JDK 1.4.2

Description:
The intermediate XML produced by the OOo plugin does not conform to the 
document-v12 DTD, even though the xsl:output element in 
openoffice-common2forrest.xsl says so. In particular:

* The intermediate document contains a <style> element inside <header>; invalid 
per the DTD.
* <p> elements contain a "class" attribute; invalid per the DTD.
* <fixme> elements do not contain an "author" attribute, though required by the 
DTD.

Steps to reproduce:
* Run "forrest run" from the plugins/org.apache.forrest.plugin.OpenOffice.org 
subdirectory of your Forrest checkout.
* Download http://localhost:8888/samples/openoffice-writer.xml and have the 
document checked by your favorite validating parser.

The trouble with this is that the FO stylesheets carry the contents of the 
<style> element over into the result tree, where they pop up as part of the 
ToC. This looks like fairly meaningless gibberish to the reader of the 
resulting PDF (etc.) document. You may verify this by checking 
http://localhost:8888/samples/openoffice-writer.pdf in the above-mentioned 
setup. 


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