[Openicc] Printing profiling targets - state of implementation?

[Till Kamppeter]

Richard, can you update your patches appropriately? For Ghostscript,
please send me a patch applying to the current GIT master (which has
your current patches already applied).

Thanks in advance.

   Till

On 05/30/2013 03:31 PM, Michael Sweet wrote:
> Till,
> 
> "off" is not a supported boolean value for third-party (i.e. not IPP/CUPS standard) options.  This will get encoded as a nameWithoutLanguage value at the IPP level and won't work like other boolean options (i.e. you won't be able to use "-o nocolor-management").  This is because some non-boolean PPD options use the value "off" for one of their choices...
> 
> So if your intent is to have a boolean option to control things, use "color-management=true" and "color-management=false" (or just "color-management" and "nocolor-management") and then in the gstoraster filter you'll need to look for "nocolor-management" in argv[5].
> 
> Another nit: for consistency, can we rename this option to "print-color-management" (to go along with "print-color-mode")? I can register this unofficially with the PWG as a CUPS extension pointing to the CUPS IPP extensions document.  That would make things:
> 
>     "-o print-color-management=true" or just "-o print-color-management" to force it on.
> 
>     "-o print-color-management=false" or just "-o noprint-color-management" to force it off.
> 
>     "print-color-management" and "noprint-color-management" in argv[5] for filters.
> 
> Thanks!
> 
> 
> On May 30, 2013, at 9:04 AM, Till Kamppeter <till.kamppeter at gmail.com> wrote:
> 
>> It is implemented in gstoraster now. Richard has sent me the appropriate
>> patch and I have applied it to the upstream GIT repository of
>> Ghostscript, so it is included in Ghostscript 9.08 and later. For
>> getting a patch for older Ghostscript versions, the patch is commit
>> c374882e38fdac.
>>
>> Inhibiting color management can be done via colord, with a command like
>>
>> colormgr device-inhibit /org/freedesktop/ColorManager/devices/<printer> 0
>>
>> or by sending the calibration print job with the option
>> "color-management=off". Please use the same option (a boolean option)
>> when adding suppression of color management to any other CUPS filter.
>>
>> Turning off color management in Ghostscript is done by calling it with
>> the "-dUseFastColor" command line option.
>>
>> Thanks to Richard Hughes for the patch.
>>
>> Richard is currently working on adding this feature to foomatic-rip.
>>
>>   Till
>>
>> On 05/20/2013 10:22 PM, Michael Sweet wrote:
>>> Edmund,
>>>
>>> We actually talked about this during the OpenPrinting summit last week;
>>> Richard is starting the work needed to make Ghostscript's gstoraster
>>> honor a "do not profile" boolean option that applications/toolkits can
>>> pass as needed.
>>>
>>>
>>> On 2013-05-20, at 4:15 PM, edmund ronald <edmundronald at gmail.com
>>> <mailto:edmundronald at gmail.com>> wrote:
>>>
>>>> Hi Guys, 
>>>>
>>>>
>>>> Some time ago, it was decided to provide a color management bypass
>>>> for printing profiling targets and other such purposes.  Has this now
>>>> been done, and if so, how does one invoke this?
>>>>
>>>> Edmund
>>>>
>>>>
>>>> _______________________________________________
>>>> openicc mailing list
>>>> openicc at lists.freedesktop.org <mailto:openicc at lists.freedesktop.org>
>>>> http://lists.freedesktop.org/mailman/listinfo/openicc
>>>
>>> _________________________________________________________
>>> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>>
>>>
>>>
>>> _______________________________________________
>>> openicc mailing list
>>> openicc at lists.freedesktop.org
>>> http://lists.freedesktop.org/mailman/listinfo/openicc
>>>
>>
> 
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>