Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
0.8
-
None
-
None
-
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.
* 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.