Apache OpenOffice (AOO) Bugzilla – Issue 21646
MS VC6: image colors corrupted when saving/loading
Last modified: 2013-08-07 14:43:36 UTC
When I paste an image from LeCroy's ScopeExplorer application into Writer, the colors are correctly displayed. However, after saving the file and reloading it, the colors are completely different. As the signals are discerned by their colors, this is a big nuisance. I include a screenshot after pasting, and a screenshot after the file was closed and reloaded. Also included a .CLP file containing the clipboard image. You can reproduce the problem by opening it using the clipboard viewer (run clpbrd.exe in Windows XP) then paste the clipboard into Writer (edit > paste).
Created attachment 10595 [details] screenshot before saving
Created attachment 10596 [details] screenshot after saving
Created attachment 10597 [details] NT clipboard file (*.clp)
Reassigned to ES
I can't reproduce this (win2000/XP). Please check the settings of your graphic device. Does this only happen in Writer? Only with the Lecroy graphics?
Hi Eric, If, by graphics device, you mean my video card: it is able to show both the "before" and "after" image, so that can't be the problem. The problem is that OOo displays a different image after reloading the file than it did before it had saved the file. It happens in Draw as well. It looks like the file has been properly *saved*, and something goes wrong when *loading*, because if I load the file in OOo 1.0.3.1 (Dutch, Windows) it is displayed correctly! Please open the attached test.sxw in OOo 1.1.0 for Windows, and check if the colors are as in before.jpg or as in after.jpg.
Created attachment 10657 [details] OOo Writer document containing image, saved by OOo 1.1.0
Ok but I still can't reproduce it... I have the same version of OOo, 2 different versions of Windows. It looks like a video card problem (together with OOo). So please try to change the settings of your card and check if this has an impact on the problem.
Hi Eric, I found that the problem only exists in the Dutch localized build. I'll try to find out what went wrong.
Yes, I tested that now in the NL build too (comapared top US and FR). Only this localized version seems to have a problem. Thus I reassing it to you. Results of some tests: this only happens with screen shots made on Windows with a 256 colors depth set in Windows. Hope this helps
Simon, any progress with this issue? It's target is 1.1.1. Can I help you with it?
Hi Pavel, I think it was caused by my compilation with MSVC++ 6 instead of MSVC++ .NET 2002. As an experiment, I made an installation set after copying all the .EXE and .DLL files of the Solver into my solver directory, and the resulting program didn't have this bug. I plan shortly trying to build 1.1.1a using a VC++ .NET (standard) compiler. I'll have to update the Dutch translation of the GUI anyway. For the final build I will replace the .EXE and .DLL files in my solver by the ones in Sun's solver, because Sun compiles them with the optimizing compiler in MS Visual Studio Professional. Anyway, thanks for the offer to help, if I get stuck I'll let you know :)
Hi Simon I can confirm this issue in brazilian portuguese build, that too is made in MS-VS6.0, but not have idea of what to make to resolve this problem. =(
I do not know JPG format to details, but could this change be cause by e.g. bit errors? Is it possible to get two version of that JPG file - before and after saving so we can binary compare them?
Hi Pavel, As far as I can tell there is no JPG in the picture here. In fact, I am pretty sure it has to do with the .PNG file format, because 1) the same problem occurs when inserting a .PNG image in a document and 2) When pasted into the document as described the image will be saved as a .PNG image: if you unzip the document you can see it contains the image as a .PNG file. If this .PNG file is opened using another program, the colors are correct, so the problem is in the displaying of the image; the data itself is not corrupted.
Volker, Sander, do you have an idea here? It does nt seems so from the first sight, but this probably is bug in our code *together* with old compiler.
so how do we proceed now ? will we switch to .Net compiler for release, fix the issue or retarget the issue to later milestone ?
the problem with "switch compiler" is that this is showing up in localised versions of OOo that "we" didn't build. so unless this is either fixed or the VC6 support is removed, this can happen again. you just need a builder with old compiler.
Retarget to 1.1.2.
*** Issue 26681 has been marked as a duplicate of this issue. ***
*** Issue 22031 has been marked as a duplicate of this issue. ***
I have expirienced the same problem many times in writer in both 1.1.0 and 1.1.1 running Win2000 Hovever it seems to depend on the file-format that is dragged in and wether the file is saved as native or word (doc) format. It might have happend in spreadsheat as well, I have not re-tested it. I have made som examples (in danish, but will be translated to englis soon) and placed them on http://www2.spejdernet.dk/taarnborg/ooo/index.html Regards, Torkil Bladt, Denmark
I did not notice the other comments first, but I can add that, the promlem is also in the danish build. It happens both when I drag and drop the image and when I load it via the menu. I do not think it has anything to do with the sxw format, as in some cases the color goes wrong already at the moment I import the file.
Hi Torkil, new danish builds should be OK. Czech team, which makes builds also for danish localization-team, replaced compiler VC6 with .NET 2002, so try any devel build from 1.1.2 line.
Thank You kwart, I look forward to ver 1.1.2, then I can be a little more convicing when talking my friends into dropping their more or les illegal MS-office installations.
cc me...
mh: I'm suggesting to close this as WONTFIX because: - we are not able to solve this for 1.1.x anyway - VC6 is old anyway - will will probably not support this compiler in the future thus it is a waste of time - both Simon and also our build system are now based on .NET2002
set to wontfix as suggested. please feel free to reopen once a fix is available.
close issue.