Comment 17 for bug 660807

Revision history for this message
NoOp (glgxg) wrote :

@CH: I'm sure that LO (Ubuntu version) can be patched to fix the issue. I just tested (using an .avi) on LO 3.3.0 installed from the .deb packages from http://www.libreoffice.org/download & adding the .avi works w/o issue on Ubuntu 10.10 (32 and 64bit). The resulting .odp does not incorrectly embed the .avi into the .odp file.

I then brought up a natty 10.04 alpha test system and tried the vanilla LO 3.3.0 on that system. It exhibits the exact same behaviour; embeds the video into the .odp. I then followed the instructions for Richard's script (comment #9) and ran the script against the same. The result is that it worked; it unlinks the embeded video & the video now runs in the natty LO version.

I reckon that the real question would be: what code between openoffice.org (1:3.2.0-7ubuntu4.2) and openoffice.org (1:3.2.1-7ubuntu1) is responsible for the change? There was some discussion on the Sun/Oracle OOo lists awhile back (I was involved) to provide an 'pack & go' type impress file whereby the video/audio files would be embeded based upon a user option. To my knowledge this 'pack & go' was never implemented in standard Sun/Oracle OOo. It appears that someone on the Ubuntu/debian? side has decided to give this a try in the current versions of Ubuntu OOo and LO & it hasn't worked. Two issues (as I see it) need to be looked at/changed:

1. The code that is causing the embedding of the audio/video files in Impress (U)OOo or (U)LO needs to be identified and fixed.

2. Embeded video/audio, while a good option, should be a *user* option on save/save as. Otherwise every user will have multimeg files for their .odp's. For example, on the impress files with the .ogg I tested on https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/172262 resulted in an 18.4Mb .odp. That's not much of an issue with a small presentation, but imagine if the presentation contained many video/audio files. Again, it should be the user choice to embed or not & I'll see if I can get a better picture/clarification of the issue in the next few days.