The following comment has been added to this issue:
Author: Florian G. Haas
Created: Sun, 6 Mar 2005 2:31 PM
Body:
I've finally managed to whip up an updated version of this patch. A few
comments have been added to mark hacks and modifications that should be
reverted in the future.
I've also modified the xsl:output element in openoffice-common2forrest.xsl to
no longer include doctype-system and doctype-public attributes. I figured that
as long as the intermediate document being produced is invalid per the DTD, it
would be inappropriate to have the xsl:output element claim otherwise.
---------------------------------------------------------------------
View this comment:
http://issues.cocoondev.org//browse/FOR-433?page=comments#action_12138
---------------------------------------------------------------------
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
Fix Fors:
0.7
Versions:
HEAD
Assignee:
Reporter: Florian G. Haas
Created: Fri, 4 Feb 2005 4:06 PM
Updated: Sun, 6 Mar 2005 2:31 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
