[Openicc] printer, driver, CUPS, PPD, printing GUI, ICC-profiles, colord, Oyranos, taxi....
Richard Hughes
hughsient at gmail.com
Fri Jan 13 09:28:40 PST 2012
- Previous message: [Openicc] printer, driver, CUPS, PPD, printing GUI, ICC-profiles, colord, Oyranos, taxi....
- Next message: [Openicc] CUPS, colord, Oyranos, printer color management
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
On 13 January 2012 16:09, Kai-Uwe Behrmann <ku.b at gmx.de> wrote:
> This hook has no advantage for other CMSs
Of course, it wasn't designed for other CMSs.
> Work on a truly shareable access to colour settings was outlined in previous threads here on list.
> IMO the best is to remove this hook ASAP.
I'm not interested about discussing every nuance of a perfect
theoretical system. A CMS is not a black box you can replace as a unit
with standardised interfaces and standardized configuration, just like
you can't do that with an X server, database or even kernel. A CMS is
just _functionality_ -- users don't care how it works, the beautiful
architecture or the fact it can be replaced by something else. 99.999%
of computer users don't know what a CMS is -- and that's a totally
good thing.
My focus is making color management "just work". This is why colord is
installed on millions of computers, and why people can already click
the mouse a few times and have a color corrected scanner, display and
printer without needing to manually configure anything. It's not
perfect at all, but it's good enough for 95% of real users, and we can
slowly work on new ways to increase that number every day.
- Previous message: [Openicc] printer, driver, CUPS, PPD, printing GUI, ICC-profiles, colord, Oyranos, taxi....
- Next message: [Openicc] CUPS, colord, Oyranos, printer color management
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the openicc
mailing list