forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [JIRA] Commented: (FOR-433) plugin produces invalid intermediate documents
Date Thu, 31 Mar 2005 22:35:18 GMT
The following comment has been added to this issue:

     Author: Ross Gardler
    Created: Thu, 31 Mar 2005 4:34 PM
I've applied this patch to workaround the problem. However, we still need to address the cause.

Progress on the technique for skinning sites looks like it will provide a long term solution.
View this comment:

View the issue:

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

     Status: Unassigned
   Priority: Major

    Project: Forrest
   Fix Fors:

   Reporter: Florian G. Haas

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

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

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message