Bug #69717 for OpenOffice-OODoc: createImageElement does not update META-INF/manifest.xml

Sat Jul 23 06:59:03 2011 gerard [...] jongerhuis.nl - Ticket created

Subject:

createImageElement does not update META-INF/manifest.xml

createImageElement does not update META-INF/manifest.xml my $newImage = $dest_doc->createImageElement( "proef", attachment => $dest_doc->getParagraph(1), size => "3.5cm, 3.5cm", style => "fr3", import => $pictName ); Solution fix it by hand my $manifest = OpenOffice::OODoc::Manifest->new( file => TEMP); $manifest->setEntry( $pictName, 'image/png'); $manifest->save;

Sat Jul 23 07:39:20 2011 jmgdoc [...] cpan.org - Correspondence added

On 2011-07-23 06:59:03, gjongerh wrote :
Show quoted text

> createImageElement does not update META-INF/manifest.xml
>
> my $newImage = $dest_doc->createImageElement(
> "proef",
> attachment => $dest_doc->getParagraph(1),
> size => "3.5cm, 3.5cm",
> style => "fr3",
> import => $pictName
> );
>
> Solution fix it by hand
> my $manifest = OpenOffice::OODoc::Manifest->new( file => TEMP);
> $manifest->setEntry( $pictName, 'image/png');
> $manifest->save;

It's not a bug; it's a functional constraint, due to the logical separation made by OODoc between the different workspaces.
<br>
When an image is inserted through the content workspace, the manifest workspace is not affected. As a general rule, a workspace is never silently changed.
<br>
Developers who are not comfortable with this constraint should have a look at ODF::lpOD, that provides similar features as OpenOffice::OODoc but allows the applications to ignore (in most cases) the workspace separation and to regard the whole document as a single object.

Sat Jul 23 07:39:21 2011 The RT System itself - Status changed from 'new' to 'open'

Sat Jul 23 07:39:50 2011 jmgdoc [...] cpan.org - Status changed from 'open' to 'resolved'