Apache OpenOffice (AOO) Bugzilla – Issue 48650
embedded excel diagrams aren't imported correctly; have black background in OO
Last modified: 2013-08-07 14:43:03 UTC
The (to be) attached word document is not rendered correctly by OO 1.9.79. For example: The background of the embedded excel diagram is black, not white (or transparent). OO should render that as MS Word does.
Created attachment 25754 [details] Word document
Created attachment 25755 [details] How it is rendered in Word
The background is stored this way in the doc format. When I open the attached document in MS Word (tested with Word 2002 and 2003), it also shows black background. When I once activate the Chart object in Word it is corrected and will also show correctly then in OO.
Closed.
Created attachment 25786 [details] I think I messed up the word file. I just reattached the word file. Reopening the bug. The doc was generated on Mac OS X btw.
As written in the comment for the new attachment: I think I "destroyed" the old file while saving it in OO. The new file is displayed correctly with Word (Windows, Mac) but not with OO on Windows.
MRU->SJ: take the second attachment; there you can see, that the background is erroneously displayed black in OO.
sj->mru: this issue has been fixed with a previous bugix, it can be tested on master.
sj: this issue 9is ready to be verified on master.
Yes, that's right. Has been fixed together with a different taks. Looks good now in 680m106 build.
Using build 680.109 on Windows the background is still black. Are you really sure that this bug is fixed?
I'm using OO.org 2.0 on Fedora Core 4 (with the latest updates) and the described problem is still there. Reopening this bug. Please tell me if you have problems reproducing it.
Changed the target, OOo2.0 is released, therefore the target must be changed.
MRU->SJ: the problem reappears. I checked it with 680m145 build on Win32 and the background of the MS OLE object is displayed black in OO.
accepted
I just imagined that this issue is double to issue 63660. I will try to fix it within the next product patch. *** This issue has been marked as a duplicate of 63660 ***
closed