forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sjur N. Moshagen (JIRA)" <j...@apache.org>
Subject [jira] Created: (FOR-1100) odt file from OOo output plugin incompatible with OOo *input* plugin
Date Thu, 28 Aug 2008 08:31:44 GMT
odt file from OOo output plugin incompatible with OOo *input* plugin
--------------------------------------------------------------------

                 Key: FOR-1100
                 URL: https://issues.apache.org/jira/browse/FOR-1100
             Project: Forrest
          Issue Type: Bug
          Components: Plugin: input.odt, Plugin: Output.OOo
            Reporter: Sjur N. Moshagen


An odt document created using the OOo output plugin used as a source document for Forrest
(and parsed using the OOo *input* plugin) renders an empty page in Forrest.

The text of the parsed OOo document reaches the xml stage, but all structure is lost or garbled,
and the text disappears in the transform to HTML.

I don't know whether the error is in the output or input plugin, but it is a desirable goal
to have roundtrip compatibility between the two plugins.

In my use-case I'm producing an odt document from a jspwiki source file, to share with MSOffice-centric
people. When I get their modified version back, I would like to convert it back to jspwiki
by using the OOo inpug plugin (I'm writing my own jspwiki *output* plugin at the moment, for
this exact purpose), to make it easy to do textual diffs, have proper version control over
the document, etc. The conversion won't be perfect, but close enough.

As long as there is this incompatibility between the OOo plugins, I'm not able to do this
roundtrip.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message