<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><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#c16">Comment # 16</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 <span class="vcard"><a class="email" href="mailto:Thomas.Freitag@alfa.de" title="Thomas Freitag <Thomas.Freitag@alfa.de>"> <span class="fn">Thomas Freitag</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=34053#c14">comment #14</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=34053#c12">comment #12</a>)
> > You have to render in
> > CMYK (because the profile in OutputIntents is a CMYK profile).
>
> I don't understand that, we have some code around that converts CMYK->RBG,
> no? Why do i need to render in CMYK?</span >
Because the profile in OutputIntents is a CMYK profile, the
transform->doTransform will give as CMYK values. If You render in RGB,
GfxICCBasedColorSpace::getRGB will be called, which then will not use the
transformation but will call alt->getRGB(), so You will loose the effects.
But during writing this I got another idea: We can examine the colorspace of
the output device (or if YOu want the former display profile) and can use
cmsCreateMultiprofileTransform with the
icc profile of colorspace -> icc profile of output intents -> display profile
to get RGB values. Then we also need no SPLASH_CMYK for this case...</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>