Re: Equal Rights for Named Untagged (Device) Spaces!!!!!!
Re: Equal Rights for Named Untagged (Device) Spaces!!!!!!
- Subject: Re: Equal Rights for Named Untagged (Device) Spaces!!!!!!
- From: edmund ronald <email@hidden>
- Date: Wed, 26 Aug 2009 10:18:32 +0200
Hi Karl -
You have hit the nail on the head - there is a clear need for a color
management OFF button that allows data safe and unmodified passage
through the print system.
I'm not advocating that -yuck, curves! -- should be handled by the
printing path, just that power users who want to go there now, just
like profilers printing targets, need to have the CM switched OFF.
Device space is of real significance to engineers and maintenance
personnel even if it is not relevant to the press trade, and there is
a need to provide licit cle"engineering access" to the print system.
The current state of play at Apple according to Eric Chan, where the
OFF switch is undocumented is not a good approach.
Edmund
On Wed, Aug 26, 2009 at 9:51 AM, Karl Koch<email@hidden> wrote:
> Hi Edmund,
>
> I would rather advocate a "switch" that allows for printing tagged,
> untagged, wrongly tagged, unknown … data without any color conversion in
> the application, the OS, the driver or the RIP. This would provide for a
> controlled way of printing color management targets and any other stuff you
> want to print "native" for whatever reason.
> I think that the application you described has nothing to do with color
> management (yuck, curves ;-)) and is so exotic that there is no need for a
> general mechanism in a color managed system to handle these curves. This
> should be done on application level.
>
> Best regards,
>
> Karl
>
> Am 25.08.2009 um 21:36 schrieb edmund ronald:
>
>> Hi Folks,
>>
>> Color untagged (device) spaces are useful. As an engineer, I'm now
>> involved in packaging a printing backend based on CUPS/Gutenprint. If
>> as a print system packager or as a color consultant I load in a set of
>> ink-curves (C), this backend will print. In some fixed reproducible
>> but not colorimetrically known way. Now someone may in due course
>> decide to profile the effect of the set of curves (C) on a given media
>> on a given sample of the printer; however for engineering purposes,
>> the backend's behavior is totally defined as soon as the ink curves
>> are locked in. The only tag I really need to send to the print system
>> in order to reproduce this behavior is the name of the curves, namely
>> (C).
>>
>> I hope this reasoning strikes a chord among some of the people in
>> charge of designing the print driver interface at Apple. Please offer
>> users the freedom to send untagged files to a print device, possibly
>> with some additional "tag name" which can be chosen to be interpreted
>> as a name rather than enforced as a colorimetric space.
>>
>> Edmund
>>
>> PS. This follows up on a private discussion with Robert Krawitz,
>> principal author of Gutenprint; although Robert is a much more careful
>> and polite man than I, he does agree there is a necessity for being
>> able to propagate untagged device data straight through the print
>> system with no "color management" applied.
>> _______________________________________________
>> 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
>
>
_______________________________________________
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