Re: [matplotlib-devel] release strategy and the color revolution

[gary r. <gar...@gm...>]

I guess you could just load some test patterns into any commercial software
graphics or design package that supports color gamut alarms, and try some
typical printer settings to make sure that the candidate color maps aren't
excessively blowing the boundaries. I'm not advocating that the default
color map needs to be perfectly reproducible in print, but it might be
worth sanity checking this; it might mean avoiding bright greens and
yellows for example. I see that PIL/pillow contains littlecms support and I
see its ImageCms.py file contains a GAMUTCHECK flag, so it might be
possible to use that, along with some common icc profiles to automate the
checking, or build it into an optimiser as a constraint.

On 6 April 2015 at 15:57, Nathaniel Smith <nj...@po...> wrote:

> On Apr 5, 2015 8:29 PM, "gary ruben" <gar...@gm...> wrote:
> >
> > Just wondering whether anyone has suggested checking candidate colormaps
> against typical printer color gamuts?
>
> How would you go about doing this in practice? Is it even possible to
> choose a subset of sRGB space and have printers take advantage of that when
> doing gamut mapping? (I guess I always assumed that printer gamut mapping
> applied to an RGB image would map all of RGB into their gamut, so there
> would be no advantage to restricting oneself go a subspace. But maybe I'm
> wrong -- color management is pretty fancy these days.)
>
> -n
>