
UPDATE: A personal communication with Paul suggests that indeed, color profiles typically do not predict color coordinate values within 1DE (a measure of colorimetric distance). I would have assumed (for high quality printers) the ICC profile is reliable, is that the case? If we can trust the printer ICC profiles that map CIELAB->CMYK then we should need to do this if we (implicitly) send CIELAB values to the printer. Why doesn't this quite answer the question? His writeup assumes that the printer is a blackbox and he calibrates output with the X-rite "ColrMunki" spectrometer. He get right to the main question in this very accessible and detailed writeup (with full code posted on his site): Is there something about reproducibility between printers I am not taking into account?ĮDIT: Paul Centore has some wonderful tools and write ups on his site: Is there a more clever way to create such a color reference? One would think it would have been done long ago if it was this easy. I am not sure if this could be problematic with two hops. I suppose one can just start by sampling CIELAB and then converting to a standard RGB colorspace then printing. Vector formats like SVG do not yet reliably implement specifying colors in colorspaces like CIELAB. One problem is that most color profile workflows deal with matching the monitor to the printer, while what we want to do here is send the right CIELAB values so that two sheets from the same printer match (assuming their CIELAB->CMYK profiles are correct). It should be easy to create a sheet that can reliably be printed on most printers though, shouldn't it? I.e a PDF with vector images (to avoid rasterization artifacts) of colored squares (with Munsell labels) that comes from a regular sampling of some volume of CIE Lab (we don't really need the really saturated chips, matching near neutral colors is more useful).

Munsell color reference chips are really useful for painters but awfully expensive.
