|
The 30" ACD falls substantially short of the AdobeRGB gamut, in particular in the green and cyan. It does cover (even slightly exceed) most of sRGB, though, except for the saturated magenta range. Hence, no amount of arm twisting is going to make AdobeRGB tagged images look real, if and when they contain those saturated greens and cyans. Something's gotta give. That's where rendering intents come into play, which let you choose the lesser evil for your purpose.
You can choose between accurately displaying those colours that can be displayed while dropping the undisplayable colours on the floor (colorimetric), or shifting and squeezing everything around to achieve a similar overall look (perceptual).
The actual working space of image editing software is always XIE or Lab, and floating point, only when you ask the software to display integer RGB values (like with the eye dropper) it'll convert the real colour (XIE or Lab) into the corresponding values from your chosen colour space. It does not matter what space that it, the software will always reverse-apply the display device profile to make up for the display's shortcomings and show the image as accurate or realistic as possible on your screen, depending on the rendering intent. That's true for colour managed systems anyway, which I believe all OSes in this day and age are? Mac OS certainly is.
To deal with not colour managed web browsers, which apparently a large number of people still use, it is safest to convert the image RGB values into the sRGB space. Most displays can be set to respond like something close to sRGB. Also, colour managed browsers will assume sRGB if an image isn't tagged with any colour space at all.
Cheers
Steffen.
|