[argyllcms] Re: Icclink does not honor rendering intent specification

  • From: Graeme Gill <graeme@xxxxxxxxxxxxx>
  • To: argyllcms@xxxxxxxxxxxxx
  • Date: Wed, 21 Feb 2007 10:59:18 +1100

Breton Roger wrote:

Maybe it's me but I used the following to link two profiles together

icclink -v -ir -or profileA.icc profileB.icc devLink.icc

I got the following output:

I'm linking a CMYK proofer profile and a monitor RGB profile.

When I view the resulting profile with ICC Profile Inspector, there are
6 tags in all in the profile: desc, cprt, pseq, clrt, clot and A2B0.

I am puzzled as I believe I have requested RelativeColorimetric in the
rendering intent. But the presence of A2B0 suggests I am not getting
RelCol? I was expecting A2B1, not A2B0.

Device links don't create multiple intents, they create a single
link, and it always uses the default table A2B0 (See table 21,
page 28 of the ICC V4.2 spec).

> I was also expecting the Intent
tag in the profile header to read "Relative", but it's reading

Sorry, I've not attempted to set the header intent to anything
smart in the current version, it's simply copied from the output
profiles header rendering intent. It should make no difference
what it's set to - functionally everything dealing with device
links will ignore it.

Graeme Gill.

Other related posts: