[Openicc] CUPS Color Management under Linux gets into distros

[Hal V. Engel]

On Wednesday, February 09, 2011 11:33:36 PM Kai-Uwe Behrmann wrote:
> Am 10.02.11, 15:40 +0900 schrieb Koji Otani:
> > From: Till Kamppeter <till.kamppeter at gmail.com>
snip
> > pdftoraster doesn't support OutputIntent now,
> > INTENT_RELATIVE_COLORIMETRIC is hardcoded.
> 
> Please note, the PDF OutputIntent is a literal ICC profile. This is
> confusing as its is different from the ICC term "rendering intent", which
> describes the prefered gamut mapping between two ICC profiles.
> 
> citation from Leonard Rosenthol, Mon Feb 7 2010 at 16:51:42 PST:
> > OutputIntent doesn't convert anything.  It serves two purposes in PDF/X,
> > PDF/A and PDF/E - and NO PURPOSE  in a standard PDF (since the spec says
> > it should be ignored).   The two uses are:
> > - Destination Profile for the target device (should you need to retarget)
> > - Source Profile for any DeviceXXX colored object(s)
> 
> Let me reformulate the question.
> Will poppler colour convert the PDF to a destination
> profile which is embedded in a PDF/X (/A, /E) as "OutputIntent" ?

No poppler has an API that allows the calling program to set the output 
profile.  It does not correctly support PDF/X at this point since it does not 
support OutputIntent.

> 
> > Should it take OutputIntent from cupsRebderingIntent Page Device
> > Attributes in PPD ?

No.  These are different things.

> > 
> > As Mr. Engel 

No need to be so formal please call me Hal.

> > wrote, poppler doesn't support rendering intent in PDF
> > content, INTENT_RELATIVE_COLORIMETRIC is hardcoded in it.
> > This is because that too many changes on poppler were needed
> > when I created patch for poppler.
> 
> Thanks for clearifying about the current state for the rendering intent in
> poppler.
> 
> kind regards
> Kai-Uwe Behrmann
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/openicc/attachments/20110210/d4fe740d/attachment.html>