<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Poppler doesn't display text in separation colorspace with alternate colorspace DeviceGray" href="https://bugs.freedesktop.org/show_bug.cgi?id=92381#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Poppler doesn't display text in separation colorspace with alternate colorspace DeviceGray" href="https://bugs.freedesktop.org/show_bug.cgi?id=92381">bug 92381</a> from <a class="email" href="mailto:Thomas.Freitag@alfa.de" title="Thomas Freitag <Thomas.Freitag@alfa.de>"> Thomas Freitag</a> <pre>Sorry for any confusing comments before. I made a lot of tests with acrobat and wondered about the results until I figured out what is the reason, s. chapter 8.6.6.4 of the spec: At the moment the colour space is set to a Separation space, the conforming reader shall determine whether the device has an available colorant corresponding to the name of the requested space. If so, the conforming reader shall ignore the alternateSpace and tintTransform parameters; subsequent painting operations within the space shall apply the designated colorant directly, according to the tint values supplied. Since the colorant is Black and this is always available, alternateSpace and tintTransform parameters must be ignored and the tint value is used to paint on the Black colorant directly. So my former patch was definitely wrong and I will provide a new one according to this spec.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>