Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#9 problem with oo 3.2.0 and images

open
nobody
None
5
2010-02-24
2010-02-24
Anonymous
No

Hi, everybody
I've found a nasty behavior. Consider an odt file with

{image1}

on opening OO gives you "corrupted file" warning but fix it.

in odf file with

{image1} {image2}

on OO give you a "corrupted file" warning and fix only the first image.

I dug in with a xml explorer the original and fixed content.xml and found out that the original have the images in a text tag
while the fixed has all the images out of text tag and listed as siblings.

Discussion

  • Yes, fixed files has image content outside text tag. However problems seems to be inside the compression and not in.the tag position. If you edit the corrected file, it seems that the image file has been renamed.
    And if you try to edit the build odt file before repair is done, you will see the file is corrupted and can't be modified (try to edit file content.xml for example).
    So i suppose problem is in zip function.
    What version of proxy do you use phpzip or pclzip ?

     

  • Anonymous
    2010-05-11

    Well actually the zip function is not the problem.

    The images need to be listed in the manifest.xml file.

    I posted a fix in the forums: http://www.odtphp.com/forum/viewtopic.php?f=5&t=147

     
  • A patch is now in SVN repository. Fix will be availabel with next release.