But I have no clue as to what you’re talking about.
Right, well, one more time expaned and enlarged -:)
Anybody in development you talk to, anytime and anywhere you talk to development, the first point that is positioned is that colour management is no more and no less than colour management.
If you have a bad exposure, well, you have a bad exposure. Colour management does not correct your bad exposure, it simply maintains the colours by morphing the colourants.
ICC colour management is based on seven categories of the ICC file format divided into two classes, the device class and the non-device class.
1. The device class is SCNR Scanner (for scanners and cameras), MNTR Monitor, and PRTR Printer.
2. The non-device class is SPAC Colour Space, ABST Abstract, NMCL Named Colour, and LINK Device Link.
The ICC architecture is based on the concept that the manner in which the colours are managed and the colourants are morphed is determined when the ICC profile is built.
The concept is that you configure, calibrate and characterise the devices over which you have control, and publish your characterisations (ICC profiles) in one of two ways.
Either you embed the characterisations into objects (e.g. TIFF, JPEG) or objects that are themselves embedded in page descriptions, or you publish the characterisations as files for others to use.
For instance, if you define a level of gray in a linearised RGB space such as Generic RGB Profile, you can soft-proof how that gray appears using the characterisation/profile for the printing condition.
Throughout, you are not changing the colourants in your object. Rather, those colourants are inviolate and intact since the conversion for the ColourWorld is in memory only.
Now, if you do need to change the colourants in order to correct your exposure, then your characterised display let's you do that in true colour.
Your object will have colourants whose colours are defined by the source ICC profile in the object, and the system will construct a ColourWorld for you to see those colours on your display.
If you open an image in Apple Preview or in Apple Pages, you can correct the exposure because the system honours the embedded profile or assigns a profile which you can change if you want.
Your colour correction controls are relative to the source ICC profile (not, of course, to your destination display profile).
When you save your colour correction, whether in Preview or Pages, you have changed your colourants relative to embedded ICC characterisation/profile for that object.
Now, a lot of people can follow this without bending over backwards, and I'm sure you can if you try. Object-oriented ICC imaging, object-oriented Unicode imaging, page markup models such as HTMl and page description models such as PDF have not the slightest to do with physical paper, so you have a choice between getting with the program or going back to physical paper. I'm sorry, but that is the reality, stark as it seems.
/hh