Bug 232334 - ps2pdf ignores transfer functions in the gradient
Summary: ps2pdf ignores transfer functions in the gradient
Status: NOTIFIED LATER
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: PDF Writer (show other bugs)
Version: master
Hardware: All All
: P2 normal
Assignee: Ray Johnston
QA Contact: Bug traffic
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-02-14 05:11 UTC by Alex Cherepanov
Modified: 2007-12-13 12:55 UTC (History)
0 users

See Also:
Customer:
Word Size: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Cherepanov 2001-02-14 05:11:18 UTC
Originally reported by: alexcher@users.sourceforge.net
ps2pdf ignores transfer functions in the shaded fill but
uses them for vector objects. The following sample program
has 2 shaded fills and 2 rectangles that should have the
same color as the left end of the shaded fill.

%!
<</PageSize [612 200] /Policies<</PageSize 1>> >>setpagedevice
612 1 scale
/grad
  { gsave
    0 0 1 100 rectclip
    <</ColorSpace [/DeviceCMYK]
      /Domain [0 1]
      /Coords [0 0 1 0]
      /Extend [false false]
      /Function
        << /FunctionType 3
           /Domain [ 0 1]
           /Functions
             [ << /FunctionType 2
                  /N 1
                  /C0 [ 0 0.5 0 0 ]
                  /Domain [ 0 1]
                  /C1 [0.5 0 0 0]
               >>
             ]
           /Bounds []
           /Encode [0 1]
        >>
      /ShadingType 2
    >> shfill

    0 0.5 0 0 setcmykcolor
    0 0 0.1 50 rectfill
    grestore
  } def

grad
{1 exch 2 div sub} settransfer
0 100 translate
grad
showpage



Comment 1 Ray Johnston 2001-04-05 13:16:06 UTC
Comment originally by rayjj@users.sourceforge.net
Logged In: YES 
user_id=11206

We acknowledge that this is a valid issue, but we do not have
resources available to address this at this time.

This problem report has been moved to doc/Issues.htm where it
may remain open for some time. Relevant comments are
captured there along with the ID# of this report.

By moving this issue to the widely distributed Ghostscript
documentation, we wish to make this issue well known and
solicit help in improving Ghostscript in this area.

Thanks for your input!