[Openicc] CUPS Color Management under Linux... (what is to do ?)

[edmund ronald]

Look guys, Chris wrote the same thing in the first post of this thread
see below.

Chris spoke----------------

Could come in handy to enable proofing at a system level. But still
guys, I think we need to keep this implementation constrained and
realistic, not overly complicated. There's enough going on as it is,
and still some pretty basic considerations need to be agreed upon.
Basic considerations about system architecture, library dependencies,
databases, etc., that I know nothing about.

I think it's fine to think about a 1.0, 2.0 and 3.0 version so that
your 1.0 implementation doesn't box you into an impossible rewrite
when it comes to 2.0 and 3.0. But really, unlike many things, there is
an "end in sight" for color management implementation. But the biggest
impediment is getting agreement about components. If everyone starts
making their own implementation, then it will be yet another fractured
color management system that won't work very well except with very
specific distributions. I don't think that's very interesting. I think
fixing the problems most people have is interesting.

-------------------




On Fri, Feb 18, 2011 at 6:54 AM, Graeme Gill <graeme at argyllcms.com> wrote:
> edmund ronald wrote:
>>
>> You know guys, Color Management would have a much better chance of
>> working if the models were clear and simple. Complex models guarantee
>> nobody apart from you guys understand the issues, and guarantee that
>> many implementations will be broken.
>
> There's a really simple way of providing what you seem to want
> Edmund - HP & Microsoft solved it for you quite a while ago. Simple
> interchange everything as sRGB. That's what all the consumer and
> office stuff currently tries to do, so I guess there's no
> problem to be solved here.
>
> Graeme Gill.
> _______________________________________________
> openicc mailing list
> openicc at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/openicc
>