http://bugs.winehq.org/show_bug.cgi?id=11532
Lars Tore Gustavsen lars.tore@mulebakken.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lars.tore@mulebakken.net
--- Comment #8 from Lars Tore Gustavsen lars.tore@mulebakken.net 2008-02-19 14:25:31 --- Hello everybody
I have just tested this on one of my computers. I normally have a color managed workflow with other tools but it was interesting to test the photoshop beast. I also have a spectrometer and a few colorimeters so I have my own monitor profiles. I tried the above adobe gamma route, but I also give up.
Instead the most obvious way was off course to replace the sRGB\ Color\ Space\ Profile.icm in ~/.wine/drive_c/windows/system32/spool/drivers/color/ with my monitorprofile. And copy the srgb profile to a new name cp sRGB\ Color\ Space\ Profile.icm /.wine/drive_c/windows/system32/spool/drivers/color/new-srgb.icc
In photoshop color settings, can I now read in the drop down boxes for RGB colorspace: Monitor-RGB-mymonitor.icc In the same dialog I set the working space to other than my monitor profile And since the dialog display the internal name of the profile the sRGB IEC61966-2.1 name is actually picked up from the new-srgb.icc file from above copy command, and it is safe to use as a workingspace.
My display profiles description is in this case the file original file name. When I load an image they are nicely viewed with my monitor profile. I must as an addition load the lut table by hand with tools like dispwin.
I would suggest for future that wine read the xicc atom like gimp and others. Se http://www.burtonini.com/computing/x-icc-profiles-spec-0.2.html The openicc mailing list is a very nice place for discussion about that kind of questions. I would suggest that some of the wine developers join that list.
This was tested with cs2 in tryout mode on ubuntu 7.10.
Regards Lars Tore Gustavsen