diff options
| author | Michael Vrhel <michael.vrhel@artifex.com> | 2010-04-28 21:43:24 +0000 |
|---|---|---|
| committer | Michael Vrhel <michael.vrhel@artifex.com> | 2010-04-28 21:43:24 +0000 |
| commit | f509e55e0962e90d0a4e31061575859eaf9f0094 (patch) | |
| tree | a21b7e778dbe6e69e588833e1fdf571e8e1cea02 /gs/base/lib.mak | |
| parent | dc7446fca824642c71002157650cf4a421feb3fc (diff) | |
With this commit we now have icc color management for CMYK components when they are members of a DeviceN color space. To understand why this is needed, consider the example where I have a device with CMYK + O and I have a DeviceN color in the document that is specified for any set of these colorants, and suppose that I let them pass through without any color management. This is probably not the desired effect since I could have a DeviceN color fill that had 10% C, 20% M 0% Y 0% K and 0% O. I would like this to look the same as a CMYK color that will be color managed and specified with 10% C, 20% M 0% Y 0% K. Hence the CMYK values should go through the same color management as a stand alone CMYK value. This feature has been requested to me by several customers in their feedback of the icc development.
git-svn-id: http://svn.ghostscript.com/ghostscript/branches/icc_work@11147 a1074d23-0009-0410-80fe-cf8c14f379e6
Diffstat (limited to 'gs/base/lib.mak')
| -rw-r--r-- | gs/base/lib.mak | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/gs/base/lib.mak b/gs/base/lib.mak index 7923187e5..54506eae5 100644 --- a/gs/base/lib.mak +++ b/gs/base/lib.mak @@ -594,7 +594,8 @@ $(GLOBJ)gxcmap.$(OBJ) : $(GLSRC)gxcmap.c $(GXERR)\ $(gsccolor_h)\ $(gxalpha_h) $(gxcspace_h) $(gxfarith_h) $(gxfrac_h)\ $(gxdcconv_h) $(gxdevice_h) $(gxcmap_h) $(gsnamecl_h) $(gxlum_h)\ - $(gzstate_h) $(gxdither_h) $(gxcdevn_h) $(string__h) + $(gzstate_h) $(gxdither_h) $(gxcdevn_h) $(string__h)\ + $(gsiccmanage_h) $(gdevdevn_h) $(gsicccache_h) $(GLCC) $(GLO_)gxcmap.$(OBJ) $(C_) $(GLSRC)gxcmap.c $(GLOBJ)gxcpath.$(OBJ) : $(GLSRC)gxcpath.c $(GXERR)\ |