Hi,
>That sounds correct. We soft proof to the screen what the resulting
>document would look like when printed to a proofer, taking the printer
>into account. The input space can be rgb, cmyk, grey, xyz, or Lab.
Ok, now I understand. This "double proofing" capability is not in the
LittleCMS library because patents.
If you want to implement this feature, a way may be to just create
abstract profiles for each emulation layer and link them
together with cmsMultiprofileTransform. You can create such abstract
profiles using _cmsComputeSoftProofLUT() and storing the lut in a
identity Lab profile.
hAbstract = cmsCreateLabProfile(NULL)
Lut = _cmsComputeSoftProofLUT(hProfileToProof, IntentToProof)
cmsAddTag(hAbstract, icSigAToB0Tag, Lut);
return hAbstract;
I have just typed this code without checking it. I think it may work.
> IsProperColorSpace is being called from
> CreateDeviceLinkTransform(p- >InputProfile,
> p->OutputFormat, TRUE). I want to make sure there
> isn't a typo in the lcms code and that should
> be sending p- >OutputProfile instead.
It is not a typo. Such transforms have only a profile and it is
placed in input. See what documentation says about:
"
For creating a device-link transform, you must open the device link
profile as usual, using cmsOpenProfileFromFile(). Then, create
the transform with the device link profile as input and the output
profile parameter equal to NULL:
hDeviceLink = cmsOpenProfileFromFile("MYDEVLINK.ICC", "r");
hTransform = cmsCreateTransform(hDeviceLink, TYPE_RGB_8,
NULL, TYPE_BGR_8,
INTENT_PERCEPTUAL,
0);
"
Regards
Marti
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Lcms-user mailing list
Lcms-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lcms-user
