[ http://issues.apache.org/jira/browse/FOR-433?page=all ]

Ross Gardler updated FOR-433:
-----------------------------

    Fix Version:     (was: 0.8-dev)
    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. 

  was:
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. 


> OpenOffice.org plugin produces invalid intermediate documents
> -------------------------------------------------------------
>
>          Key: FOR-433
>          URL: http://issues.apache.org/jira/browse/FOR-433
>      Project: Forrest
>         Type: Improvement
>   Components: Plugin: OpenOffice.org
>     Versions: 0.8-dev
>  Environment: Tested on Debian Sarge with Linux 2.4.27 an JDK 1.4.2
>     Reporter: Florian G. Haas
>     Priority: Minor
>  Attachments: openoffice.org-plugin.20050204.patch, 
> openoffice.org-plugin.20050306.patch
>
> 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. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira