Bug 691845

Summary:	CUPS Raster output device produces incorrect color output with RGBW color space
Product:	Ghostscript	Reporter:	Till Kamppeter <till.kamppeter>
Component:	CUPS driver	Assignee:	Michael Vrhel <michael.vrhel>
Status:	RESOLVED DUPLICATE
Severity:	major	CC:	htl10, mike, till.kamppeter, twaugh
Priority:	P4
Version:	9.00
Hardware:	PC
OS:	Linux
Customer:		Word Size:	---
Attachments:	launch_leaflet.pdf out.raster

Description Till Kamppeter 2010-12-17 21:01:31 UTC

Created attachment 7043 [details]
launch_leaflet.pdf

If I use the CUPS raster output device ("-sDEVICE=cups") with output color space RGBW ("-dcupsColorSpace=17") I get complete messed color output.

As an example one can run the following command line with the attached file:

cat ~/ghostscript/gpl/testfiles/launch_leaflet.pdf | gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH -sDEVICE=cups -sstdout=%stderr -sOutputFile=%stdout -r72x72 -dcupsBitsPerColor=8 -dcupsColorSpace=17 -_ > out.raster

The resolution does not need to be high for this test, as it is a pure color problem.

You can visualize the result with rasterview from

http://www.easysw.com/~mike/rasterview/

I have done the test with GS 9.00 under Ubuntu Natty.

Comment 1 Till Kamppeter 2010-12-17 21:05:09 UTC

Created attachment 7044 [details]
out.raster

The CUPS Raster output of the example command line.

Comment 2 Till Kamppeter 2010-12-17 21:07:21 UTC

Important to note is that the problem did not occur with GS 8.xx and also does not occur with GS 9.00 for normal RGB ("-dcupsColorSpace=1").

Comment 3 Michael Vrhel 2010-12-17 22:01:28 UTC

This is caused by the same issue as 691760.  Bascially the RGBW device is getting the CMYK device profile assigned to it.  For these unique color spaces we will likely generate a device profile to use based upon the device color mapping procs.  If proper output is desired immediately, a device profile could be specified on the command line for ghostscript for this color space.

*** This bug has been marked as a duplicate of bug 691760 ***