forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [JIRA] Commented: (FOR-310) Support embedded open office images (and Impress files)
Date Wed, 03 Nov 2004 19:37:38 GMT
The following comment has been added to this issue:

     Author: Clay Leeds
    Created: Wed, 3 Nov 2004 1:37 PM
Here's a list of some issues I still see with the plugin, which I assume can
be handled through updates to Forrest's XSLT stylesheet openoffice-writer2forrest.xsl:

- workaround for the OOo style sheet issues
- funky handling of list items, especially with list item nesting;
- embedding and/or linking images;
- handle image 'name' properties vis a vis OpenOffice & Forrest output
  (Currently the 'name' attribute accessed via 
   Graphics Properties > Options > Names > Name
   defaults to Graphic[#] and is always displayed.
   I'd like to turn this off because it is *not*
   shown in OOo so I have to provide a CAPTION. But
   if provide a CAPTION, I get both the CAPTION and
   the 'name' property in Forrest output)
- a system for managing multiple image resolutions
View this comment:

View the issue:

Here is an overview of the issue:
        Key: FOR-310
    Summary: Support embedded open office images (and Impress files)
       Type: New Feature

     Status: In Progress
   Priority: Major

    Project: Forrest
   Fix Fors:

   Assignee: Ross Gardler
   Reporter: Ross Gardler

    Created: Wed, 6 Oct 2004 1:16 PM
    Updated: Wed, 3 Nov 2004 1:37 PM

The attached files provide provide support for embedded images in Open Office documents and
for Open Office Impress documents.

They also provide the start of support for relvant style information, scuh as Bold, italic

However, these files were created against a fairly old version of Forrest and it is not a
simple case of committing the changes anymore. They need to be carefully merged with current

It is recomended that this be done as part of the excercise to create an Open Office plugin
so as to not to cause any disruption in trunk.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message