|
Sorry I did not respond earlier. Admittedly I do not check this forum very often K
A color space is not the same as a color model. These terms are often mixed up and it creates lots of confusion.
CMYK and RGB … are color models not color spaces. sRGB, AdobeRGB, ColormatchRGB and US WEB Coated (SWOP) v2 are color spaces.
“A color model is an abstract mathematical model describing the way colors can be represented as tuples of numbers, typically as three or four values or color components (e.g. RGB and CMYK are color models). However, a color model with no associated mapping function to an absolute color space is a more or less arbitrary color system with little connection to the requirements of any given application.”
http://en.wikipedia.org/wiki/Color_space
Device color profiles and image color profiles are not the same thing. A device profile profiles the output of the device so that the rendering intent of the device is honored and an image color profile does the same for the image. By comparing both the image and device profile rendering intents can be maintained.
If you swap the color profile of an image you are changing the rendering intent. The device profile needs to match the way the device outputs color. No one would think it a good idea to swap the profile of a printer either unless you also did something to the printer, like change the ink set.
…Like the printer, the image needs to be converted to the target profile if the profile is changed and you don’t want to mess up your rendering intent. This is what Lead does not do and should. It is a big deal to do, and you need a color engine to do it, but it is really important if you want to maintain the rendering intent and say you support color management.
Your developers may find this a useful starting point when they go to look for a color management engine that they can implement. http://www.littlecms.com/
|