<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Poppler ignores rendering intents and always uses INTENT_RELATIVE_COLORIMETRIC" href="https://bugs.freedesktop.org/show_bug.cgi?id=34053#c22">Comment # 22</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Poppler ignores rendering intents and always uses INTENT_RELATIVE_COLORIMETRIC" href="https://bugs.freedesktop.org/show_bug.cgi?id=34053">bug 34053</a> from <a class="email" href="mailto:Thomas.Freitag@alfa.de" title="Thomas Freitag <Thomas.Freitag@alfa.de>"> Thomas Freitag</a> <pre>(In reply to <a href="show_bug.cgi?id=34053#c21">comment #21</a>) > ok, maybe something was wrong on my side, try to have a go at fixing the > crash and once that's sorted we can go again at it and see if i can still > reproduce the wrong coloring You still will be able to reproduce the wrong coloring in altona_visual_1v2a_x3.pdf. I digged into it and already encountered two problems: 1. When the patch should completely support rendering intents, we need four versions of XYZ2DisplayTransform, one for each renderíng intent and we must support this in GfxCalGrayColorSpace, GfxCalRGBColorSpace and (which is important for this PDF) GfxLabColorSpace! 2. Since You commited the usage of getRGBLine() today early morning, and the output intent is here a CMYK profile, we need to support this in lineTransform and getRGBLine(), too. With other words, the patch becomes bigger and bigger, and we probably can commit this only to master. But I'm still not completely satisfied with my current solution, so please stop any further investigation and wait until I upload a new patch which solves the altona issues completely.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>