<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#c6">Comment # 6</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>I run my new patch which I will upload in a few seconds now through a regression test and encountered 42 unexpected failures. But all of them uses a Separation colorspace with name Black, and only the gray values are slightly different. See i.e. bug-poppler25404.pdf: It uses [/Separation /Black /DeviceCMYK 12 0 R] where the function converts it first to a CMYK value and then we use GfxDeviceCMYKColorSpace::getRGB() with a complex matrix multiplication to get it back to RGB This of course results in different gray values than the new, much simpler gray calculation! So this is what I expected and can accept and is even closer to the spec.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>