Has anybody already written a basic OpenOffice Writer Output plugin?
Even though our client won't pay for it, I'd really like to do some
experimenting with typesetting larger documents with writer.
Cheers
Ferdinand Soethe
I'm planning to change the oo-writer plugin to replace native links,
that is links to writer, impress and calc files, with html-links so
that they will work seamlessly in writer and Forrest.
At the moment they are not translated so that links to another
openoffice-file will not work when exported
RG> Cool stuff - thanks. I especially like the yellow sticky notes = fixmes
Thanks. I'm impressed how easy it is to work with oo-xml once somebody
got the hard stuff like unpacking out of the way. Fun to work with!
Though I'm already having second thoughts about this new feature
because the ori
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.cocoondev.org//browse/FOR-465
Here is an overview of the issue:
-
Key
Trying to do 'forrest' in the Forrest project "docs-author" directory
reports errors at the "unpack-plugin" stage for both the pod-output
and projectInfo plugins. I do not know how to debug what is going wrong.
--David
The following issue has been updated:
Updater: David Crossley (mailto:[EMAIL PROTECTED])
Date: Mon, 14 Mar 2005 7:08 PM
Changes:
summary changed from forrest hangs with
java.lang.StackOverflowError to trying cocoon://site.xml hangs with
java.lang.StackOverflowError
[EMAIL PROTECTED] wrote:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.cocoondev.org//browse/FOR-464
Here is an overview of the issue:
---
The following issue has been updated:
Updater: Ferdinand Soethe (mailto:[EMAIL PROTECTED])
Date: Mon, 14 Mar 2005 4:20 PM
Comment:
Patch log and additional file for sample directory
Changes:
Attachment changed to patch.zip
---
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.cocoondev.org//browse/FOR-464
Here is an overview of the issue:
-
Key
Ross Gardler wrote:
RG> You could use the FIXME tag in XDoc.
Good idea. That'll really make it stand out. Will do that.
--
Ferdinand Soethe
The following comment has been added to this issue:
Author: Dave Brondsema
Created: Mon, 14 Mar 2005 12:00 PM
Body:
FAQ: "2.7. Some of my files are not being processed because they use common
filenames." needs to be updated
-
Ferdinand Soethe wrote:
Dave Brondsema wrote:
DB> Sounds like a good idea. Unfortunately, I'm not sure if there's any way
DB> for an XSL template to hook in to an error reporting system. We could
DB> just change "hugo" to be "Error: Non-Hierarchical OpenOffice.org
DB> Headings" and the user would
Dave Brondsema wrote:
DB> Sounds like a good idea. Unfortunately, I'm not sure if there's any way
DB> for an XSL template to hook in to an error reporting system. We could
DB> just change "hugo" to be "Error: Non-Hierarchical OpenOffice.org
DB> Headings" and the user would have to look at the
Ferdinand Soethe wrote:
Dave Brondsema wrote:
DB> The OO.o plugin does not properly handle headers, so you may encounter
DB> other weird issues too. I think things work best if you have an ordered
DB> heirarchy of headings, like this:
DB> heading1
DB> heading2
DB> heading2
DB> heading2
DB> heading
Dave Brondsema wrote:
DB> The OO.o plugin does not properly handle headers, so you may encounter
DB> other weird issues too. I think things work best if you have an ordered
DB> heirarchy of headings, like this:
DB> heading1
DB> heading2
DB> heading2
DB> heading2
DB> heading3
DB> heading2
DB> h
It works again, cool !
Cordialement,
Cyriaque,
Ross Gardler a écrit :
Cyriaque Dupoirieux wrote:
Hi,
With the new plug in Project Info, we lost the ability to layout
actions description.
I used - for instance - unordered list tag : ... to
clarify some complex actions in my History of modifi
16 matches
Mail list logo
