Re: Bug 687711, Add ideal CMYK color space to GS resources.

Ray Johnston <[email protected]> Fri, 01 Oct 2004 11:08:13 -0700
Newsgroups gmane.comp.printing.ghostscript.patches
Organization Artifex Software Inc.
Message-ID <[email protected]>
Alex,

Alex Cherepanov wrote:
> [/DeviceCMYK] is a way to selectively disable CIE based conversions
> for the /DeviceCMYK color space. The user doesn't need this.
> 
>> It seems that the CIEBasedDEFG that you have is equivalent to the
>> trivial case of specifying [ /DeviceCMYK ] as the DefaultCMYK
>> resource.
> 
> 
> No. Specifying [ /DeviceCMYK ] leaves CMYK colors unchanged.
> The CMYK colors will be printed later as device-dependent colors
> or displayed as simulated printed ink colors in case of Acrobat
> Reader.
> 
> The user wants to simulate the effect of the standard PostScript
> CMYK to RGB conversion as it looks on the screen in device-independent
> way to get the old colors in Acrobat Reader window and (as far as
> possible) on the printer. That's what does the proposed color space.

OK. So the user *does* want post conversion of the CMYK, but with the
simplistic CMYK assumed as the input color space. Thanks for the
clarification.

> I agree with /TrivialCMYK.

Please go ahead and commit your new color space as TrivialCMYK.

>> Also please note that in CVS log messages, there is no [COMMENTS]
>> section header.
> 
> We need a convention how to separate the text that goes to the log files
> from other rants.

The DETAILS should contain explanation of the method/algorithm, design
choices made, and limitations. We don't want general 'rants' in the
CVS log at all.

The place for general comments is in an email to gs-devel or gs-code-review,
or even Comments against the bug, but not in the cvs log. Since all of
the mailing lists are archived and the bug tracker comments are retained,
the general comments (or "rants") don't need to be in CVS log messages in
order to not be lost.

Regards,
Ray
_______________________________________________________________________