[Openicc] CUPS Color Management under Linux gets into distros

[Koji Otani]

From: Kai-Uwe Behrmann <ku.b at gmx.de>
Subject: Re: [Openicc] CUPS Color Management under Linux gets into distros
Date: Thu, 10 Feb 2011 08:33:36 +0100 (MET)
Message-ID: <alpine.LNX.2.00.1102100822460.5202 at roma.rasena>
snip
ku.b> > till.kamppeter> > Seems to me any pdftoraster filter needs to honor
ku.b> > the PDF contents,
ku.b> > till.kamppeter> > not do extra things on its own. Or we run into
ku.b> > trouble.
ku.b> > till.kamppeter> > So if this pdftoraster honors ICCBased without
ku.b> > substitution, that's
ku.b> > till.kamppeter> > good. If its implementation of CUPS ICC profile
ku.b> > support means that it
ku.b> > till.kamppeter> > uses externally referenced profiles as the
ku.b> > destination profile, that's
ku.b> > till.kamppeter> > fine *UNLESS* the PDF print spool file contains an
ku.b> > OutputIntent in
ku.b> > till.kamppeter> > which case that needs to be used. So does
ku.b> > pdftoraster support
ku.b> > till.kamppeter> > OutputIntent?
ku.b> > till.kamppeter>
ku.b> > till.kamppeter> I do not know. Otani-san, can you answer Chris'
ku.b> > question?
ku.b> > till.kamppeter>
ku.b> > till.kamppeter>    Till
ku.b> > till.kamppeter>
ku.b> >
ku.b> > pdftoraster doesn't support OutputIntent now,
ku.b> > INTENT_RELATIVE_COLORIMETRIC is hardcoded.
ku.b> 
ku.b> Please note, the PDF OutputIntent is a literal ICC profile. This is
ku.b> confusing as its is different from the ICC term "rendering intent",
ku.b> which describes the prefered gamut mapping between two ICC profiles.
ku.b> 

Ya, I was confused.

pdftoraster doesn't support OutputIntent.
---------
Koji Otani