Comment 64 for bug 885324

Revision history for this message
In , Francesco+kde (francesco+kde) wrote :

Digikam will stay with lcms1 for this release (will use lcms2 only in absence of the former).
From the next one lcms2 will be default and lcms1 deprecated to be removed after that.

Git commit 19d4c9201ccd175ed67cee0724413e087fb4b0e2 by Francesco Riosa.
Committed on 21/02/2012 at 21:40.
Pushed by riosa into branch 'master'.

[lcms2] tag buffer need initialization

M +4 -1 libs/dklcms/digikam-lcms.cpp

http://commits.kde.org/digikam/19d4c9201ccd175ed67cee0724413e087fb4b0e2

Git commit 326c8803e3740dfbd421a537b6226c2a25bd4426 by Francesco Riosa.
Committed on 22/02/2012 at 00:22.
Pushed by riosa into branch 'master'.

[lcms2] fixed a cast bug in cmsFloat2XYZEncoded()

We are now at feature parity with lcms1.
There are differences between the two implementations, they are
quantifiable even in 8bit images (1/256).

lcms2 should be more precise (and faster) than lcms1

M +1 -7 libs/dklcms/digikam-lcms.cpp
M +0 -3 libs/dklcms/digikam-lcms.h