Hi Marti,
Thanks! That was easy. :-)
Follow-up question: do you think an app should write V4 profiles by default
and only switch to a V2 profile when the user explicitly wants the output
to be backward compatible with old software? Or do you think an app should
write V2 profiles by default and switch to a V4 profile when there is a
need to take advantage of V4 features?
Terence
On Wed, Apr 12, 2017 at 3:27 PM, Marti Maria <marti.ma...@littlecms.com>
wrote:
> Hi Terence,
> It is easy. Just set the version to 2.0 prior saving. The library will do
> all necessary conversions to get a V2 compliant profile. Many V2 profiles
> are marked as using 3.4
>
> Regards
> Marti
>
>
>
>
> On 12 Apr 2017 18:29, Terence Tay <terence...@gmail.com> wrote:
>
> Hello,
>
> I am currently using LCMS to create profiles using cmsCreateRGBProfile()
> and by specifying the primaries, tone curve and white point.
>
> Then I use cmsSaveProfileToMem() to save this profile to an array of
> bytes, which is then embedded in the image format (usually JPEG or TIFF).
>
> It looks like the ICC profiles created in this way are V4 profiles. Some
> older software (like Windows Photo Viewer) don't read V4 profiles.
>
> How can I create V2 versions of these profiles?
>
> Thanks.
>
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Lcms-user mailing list
Lcms-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lcms-user
