[Poppler-bugs] [Bug 34053] Poppler ignores rendering intents and always uses INTENT_RELATIVE_COLORIMETRIC

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=34053

--- Comment #14 from Albert Astals Cid <aacid at kde.org> ---
(In reply to comment #12)
> 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?

> Two open points in my opinion: 
> 1. Because the display profile now depends on the PDF, we can't use a static
> variable for it anymore. It will not make any difference if just one
> apllication uses the poppler library at the same time, and so I would prefer
> to solve that in a second step (store the display profile in the doc
> instance and use the static as default).

You mean setDisplayProfile? As I understand that is the profile of your display
(i.e. your monitor), and yes I guess it may happen that you are running a
single instance of poppler on multiple monitors each of them with different
display profiles, but doesn't seem like an urgent need (i mean, yes let's fix
it, but it's a bit weird, isn't it?

> 2. We have now the second case where we definitely need the library compiled
> with SPLASH_CMYK (the other is the overprint usage). Shouldn't we make
> SPLASH_CMYK defined by default, and perhaps remove it completely in an
> additional step? I know that the library become bigger in size, but is this
> really such important?

This is ortogonal to this patch/bug, I'd prefer if you raise the discussion on
the mainling list, i don't have a huge opinion on it tbh.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/poppler-bugs/attachments/20130805/fd732117/attachment.html>