Re: [Gimp-print-devel] Color-managed printing on Linux with current CUPS: Fact or fiction?
Re: [Gimp-print-devel] Color-managed printing on Linux with current CUPS: Fact or fiction?
- Subject: Re: [Gimp-print-devel] Color-managed printing on Linux with current CUPS: Fact or fiction?
- From: Kai-Uwe Behrmann <email@hidden>
- Date: Mon, 30 Jan 2012 17:19:33 +0100
Am 30.01.2012 16:31, schrieb Tim Waugh:
> On Mon, 2012-01-30 at 16:18 +0100, Kai-Uwe Behrmann wrote:
>> The colord hook in CUPS is flawed in essential parts. That is not to be
>> called colour management at all.
> ... but ...
>
>> Till Kampeter connected CUPS own profile selection mechanism with
>> Ghostscript for CUPS vendor side colour management. Edmund is now on the
>> path to make that path configurable for user selected profiles.
> ... this is *exactly* how colord support is currently already
> implemented, with the ability to override based on user-supplied
> profiles already in place.
Unfortunedly the colord hook in CUPS side steps the CUPS communication
paths. It is easily possible to print with the active profile of an
other user. It was mentioned that the three selectors are not sufficient
to select the correct calibration state. Users can easily change gamma,
brightness in the print dialog and get no warning while using the same
profile. So users need practical to check each time that nothing changed
in one of the unpredictable way outlined. That kind of colour transform
is useful for testing, but too unrelyable for production. Management
implies a level of securing conditions.
In my view the not so great situation is fixable. Remove the colord hook
in CUPS and use proper available mechanisms through regular CUPS APIs.
Of course that will be a little bit more work.
kind regards
Kai-Uwe Behrmann
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden