[Openicc] colord Printing Plans, CPD and Gutenprint
Kai-Uwe Behrmann
ku.b at gmx.de
Mon Feb 28 01:09:18 PST 2011
Am 27.02.11, 22:01 -0000 schrieb Alastair M. Robinson:
> On 27/02/11 01:24, Robert Krawitz wrote:
>
>> Alastair, if we provided something like this within libgutenprint,
>> would you use it in PhotoPrint? Or is this something you see
>> PhotoPrint as doing, in which case it would make more sense to put it
>> in our CUPS driver?
>
> I don't see PhotoPrint doing this itself, but I'm undecided whether
> Gutenprint would be the right layer for querying this, even for as low-level
> a client as PhotoPrint. If gutenprint ends up bundling any profiles, then it
> would be useful for it to be able to indicate to a client app which of them
> is appropriate. Where things get messy is when custom profiles are installed
> - keeping track of that would be beyond Gutenprint's scope, and into the
> scope of colord / Oyranos, yes?
A dump out of calibration settings and a appropriate recommendation on how
to map to them ICC profile selection is a good way IMO. This has the
potential to serve as a guide for various colour management systems and on
different platforms.
(These goals where already menioned, I think and agree with.)
To remember my wishes to work nicly with Oyranos and other CMS's are:
* a key / value structure of the data
* a very simple matching algorithm (a rankmap appears simple)
* avoid obligatory programatic rules like 'if', 'when' and so on
I think as well this format can set colord under pressure to deliver more
than a three qualifier rule for user supplied profiles. This will bring
us a more robust automated profile selection. The colord author appears to
consequently ignore this demand and insist on pushing his flawed model.
kind regards
Kai-Uwe Behrmann
--
developing for colour management
www.behrmann.name + www.oyranos.org
More information about the openicc
mailing list