LCHab Conversion is Inaccurate

google-code-export / gpick

Automatically exported from code.google.com/p/gpick

2 stars 0 forks source link

LCHab Conversion is Inaccurate #77

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

The following hex color: '#00ADB0' has the following LCHab coordinates 
(illuminant 'D65'):

- with Bruce Lindbloom's Calculator:
    64.1760 37.0516 199.0531

- with python-colormath:
    64.176574 37.050265 199.063066

gpick, however, sees it as:
    63.8267 39.2738 198.9078

Original issue reported on code.google.com by nihilh...@gmail.com on 18 Mar 2012 at 2:18

GoogleCodeExporter commented 9 years ago

This issue was closed by revision 802e1083c287.

Original comment by thezbyg on 19 Mar 2012 at 7:43

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

Currently Gpick uses Lab illuminant and observer settings for LCH 
transformations. Will this be enough or should LCH have its own separate 
illuminant and observer settings?

Original comment by thezbyg on 19 Mar 2012 at 7:47

GoogleCodeExporter commented 9 years ago

I think you can have a single setting, since, as far as I understand it, LCHab 
is just a polar version of the CIELAB values.

Original comment by nihilh...@gmail.com on 19 Mar 2012 at 7:51