Pascal de Bruijn wrote:
Are there any guidelines to translate "accurate color" to "general web use", if that makes any sense at all...
It only makes sense if you define what you want. One decision is whether you are after a side by side color match or an appearance match. The first implies a side by side colorimetric match. The second implies that the viewer adapts to each viewing situation separately. Another decision is whether you are attempting to match a single color, or a range of colors. The former implies gamut clipping, the latter gamut compression. Ideally you would specify the color in its native colorspace, and tag the colorspace with an ICC profile, so that the destination can choose intent and sort out how to translate the color into the local device colorspace. If you want to send RGB values, then it's safest to assume the destination is sRGB, and tag it as such if tags are possible. If you're trying to convey a color defined by a reflective sample viewed at the destination, then a colorimetric match is doubly difficult if you don't known the actual destination illumination and display device response. An appearance match is easier, since these both correspond to white point matched intents, but the viewing conditions can only be guessed at or assumed. If you want to do gamut compression, then you have to define the source gamut you want to keep relative to each other, as well as assume a destination gamut. Graeme Gill.