[gs-bugs] [Bug 692334] New: PS3 CET file 12-07D.PS gets wrong colors on page 3 (GLOBINT)

bugzilla-daemon at ghostscript.com bugzilla-daemon at ghostscript.com
Fri Jul 8 17:23:34 UTC 2011


http://bugs.ghostscript.com/show_bug.cgi?id=692334

           Summary: PS3 CET file 12-07D.PS gets wrong colors on page 3
                    (GLOBINT)
           Product: Ghostscript
           Version: master
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P4
         Component: Color
        AssignedTo: michael.vrhel at artifex.com
        ReportedBy: ray.johnston at artifex.com
         QAContact: gs-bugs at ghostscript.com


Created an attachment (id=7657)
 --> (http://bugs.ghostscript.com/attachment.cgi?id=7657)
12-07D.PS

The file (and the slightly reduced version) show wrong colors on the Global
Interference page (page 3)

With the ppmraw device, a gray areas of images are rendered as shades of red.
Different devices show different color differences. With the pkmraw device
the images are mostly cyan.

command line:

   gswin32c -dJOBSERVER 12-07D.PS 

the default window display is RGB and shows the same thing as ppmraw. Using
-dDisplayFormat=16#20808 will have CMYK output similar to pkmraw.

I determined that this was due to the gscms_transform_color only returning a
single component (instead of 3 or 4) after gscms_transform_color_buffer was
called and changed the link_handle's OutputFormat to 1 component (from the
expected 3 or 4).

In a phone call with Michael Vrhel, we determined this is most likely due to
the 'znulldevice' procedure (which is used in this CET) setting its device
profile from the current device (e.g. ppmraw) without regard for the mismatch
between the color_info (num_components, etc.). With a different device profile,
we would have a different link handle and avoid the setting the OutputFormat
to an incorrect value.

Michael will also investigate whether or not gscms_transform_color_buffer
should ever change the num_channels rather than just warning or error on
mismatch.

I have no idea why this showed up on the tagfix branch testing but it probably
is due to the differences in the way profiles are accessed from the device.

-- 
Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the gs-bugs mailing list