Overriding tagged device spaces

This page applies to Harlequin v13.1r0 and later; both Harlequin Core and Harlequin MultiRIP.

It is possible to override a tagged device space and treat it as though it were an untagged device space. That includes replacing it with an intercept space the same as untagged device spaces. This configuration shows the use of the /OverrideCMYK, /OverrideRGB, and /OverrideGray keys:

CODE

<<
  /DeviceRGB [ /ICCBased (iccprofiles/sRGB-SWOP.icc) (r) file ]
  /BlendRGB [ /ICCBased (iccprofiles/sRGB.icc) (r) file ]
  /OverrideCMYK true
  /OverrideRGB true
  /OverrideGray true
>> setinterceptcolorspace
<<
  /Profile (iccprofiles/SWOP.icc) (r) file
>> setreproduction

Tagged RGB spaces are replaced with the sRGB-SWOP.icc DeviceLink intercept. Tagged CMYK and Gray colors are treated as untagged device spaces because these do not have intercept profiles, so their values pass through to a CMYK device without conversion.

There are some important restrictions on the use of DeviceLink profiles when used with jobs containing transparency; see Blend space color management. It is, therefore, normal to use /BlendCMYK and/or /BlendRGB keys in conjunction with DeviceLink profiles, as has been done above using a profile corresponding to the input side of the DeviceLink profile.

The override keys also apply to transparency color conversions, so all tagged RGB transparency groups are intercepted with the /BlendRGB profile.