[Openicc] Print and monitor Color Pipeline

[edmund ronald]

And after our minute of truth and rationality, we go back to
commercial programming and the way the world really works :)

Edmund

On Wed, Jan 26, 2011 at 11:51 PM, Chris Murphy <lists at colorremedies.com> wrote:
> On Jan 26, 2011, at 3:43 PM, edmund ronald wrote:
>
>> I think it is interesting to see what needs to/ deserves to be rolled
>> out initially:
>>
>> - sRGB and untagged (default2sRGB) for consumers.
>> - device RGB
>> - device CMYK
>> - maybe deviceN (real device space).
>>
>> This should solve a bunch of issues for everyone, consumers and
>> photographers wanting a non-proprietary print station. I think anyone
>> wanting to print CMYK on Linux *today* is probably able to provide
>> their own profile and convert to the destination space themselves.
>>
>> Of course, I myself only know about RGB Photo workflows, so my opinion
>> on the necessity of an initial CMYK rollout is subject to revision.
>
>
> I think RGB and CMYK are control signals, and should be abstracted away from users. I don't even like photographers dealing with RGB. It's unintuitive, clunky, and in color managed apps there's no correlation between actual RGB values and the ones displayed on screen anyway. So I'd prefer LCH based tools - or better JCH or IPT.
>
> And so you can imagine how I feel about CMYK.
>
> Chris Murphy
> _______________________________________________
> openicc mailing list
> openicc at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/openicc
>