Thomas Lunzer wrote: > Thank you for the quick reply. I get your thougt for the first step > when you create the device link, this one is not usable for icc2ps -right?
Yes. > Then you use icclink from lcms which does n o t create a device link, > instead it creates a kind of smelted profile out of the formerly > created device link and again the RGB input profile. Lcms' icclink has an option "-x" to tag a generated CIELAB -> CMYK (or RGB) device link not as device link profile but as output profile (which is of course just a "castrated" output profile, containing only a B2A table, but no A2B table - but this is sufficient ot make icc2ps happy). > So the conversion chain amounts to RGB > RGB > CMYK, where RGB > RGB > ideally should not change the result. Did I get your idea right or is > there a mistake in my thoughts? The transformation of the resulting output profile is eventually CIELAB -> RGB -> CMYK (but the RGB intermediate step is hidden). E.g. $ argyll_icclink -f -kx -G -ip sRGB.icm ISOcoated.icc link.icc $ lcms_icclink -x -o output.icc -t1 -c2 *Lab sRGB.icm link.icc $ icc2ps -o output.icc > ISOcoated_K_only_CRD.ps Regards, Gerhard ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Lcms-user mailing list Lcms-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lcms-user
