[gs-bugs] [Bug 691495] Wrong colours if GS called by GSView

bugzilla-daemon at ghostscript.com bugzilla-daemon at ghostscript.com
Mon Jul 26 04:46:38 UTC 2010


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

--- Comment #11 from SaGS <sags5495 at hotmail.com> 2010-07-26 04:46:37 UTC ---
My primary suspect was /DisplayFormat, so I tried the following:

    (a) /DisplayFormat as set by GSView, -dNODISPLAY:
    gswin32c -dNODISPLAY
             -c "<< /DisplayFormat 16#30804
                    /OutputDevice /display >> setpagedevice"
             -c "currentpagedevice /DisplayFormat get == flush"
             -f "Bug691495-[grayandred]-sample.ps"

    (b) /DisplayFormat with Ghostscript’s default value, -dNODISPLAY:
    gswin32c -dNODISPLAY
             -c "<< /DisplayFormat 16#30884
                    /OutputDevice /display >> setpagedevice"
             -c "currentpagedevice /DisplayFormat get == flush"
             -f "Bug691495-[grayandred]-sample.ps"

    (c) /DisplayFormat as set by GSView, without -dNODISPLAY:
    gswin32c
             -c "<< /DisplayFormat 16#30804
                    /OutputDevice /display >> setpagedevice"
             -c "currentpagedevice /DisplayFormat get == flush"
             -f "Bug691495-[grayandred]-sample.ps"


- (a) and (b) set the requested /DisplayFormat and show a wrong image.
- (c) displays the correct image, and does not respect the /DisplayFormat.

Note that both (b) and (c) result in the same /DisplayFormat value, the 
default one; one is OK but not the other. The difference is that (b) 
starts with -dNODISPLAY and later selects the output device, while (c) goes 
on with the default initialization. Maybe in the former case the display 
device is not initialized correctly.

-- 
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