Re: Re. inkjets: An open letter to...
Re: Re. inkjets: An open letter to...
- Subject: Re: Re. inkjets: An open letter to...
- From: Kai-Uwe Behrmann <email@hidden>
- Date: Wed, 21 May 2008 22:25:22 +0200 (CEST)
Hello,
following the idea of recording a history I applied this to tracking the
colour conversions in a process chain.
I outlined, how I think it can work on the OS level here:
https://www.oyranos.org/wiki/index.php?title=Concepts#History_tracking_for_colour_conversions
In short the used profile ID's and the used options will be embedded into
the colour transformation and the later, as a device link, into the output
profile, which can then be embeded itself into a image for instance.
So by analysing the resulting image/PDF or whatever the whole colour
conversion history can be followed in all its steps. A precondition is the
throughout use of the OS CMS, which handles the required tasks.
Some details are not yet covered. Basically is is what you, Jan-Peter,
describe for a printing chain but here on the CMS level in more general.
How a specific application, library or driver can enrich to this process
information chain would be nice to define in a common sense. So tools for
analisis work cross platform just like the ICC profiles does already
today.
The proposed architecture alowes only for observing, but I hope in much
detail.
kind regards
Kai-Uwe Behrmann
--
developing for colour management
www.behrmann.name + www.oyranos.org
Date: Tue, 20 May 2008 11:30:21 +0200
From: Jan-Peter Homann <email@hidden>
> Hello Lars, Tom and list
> In the print chain, we have the possibility of colormanagement at:
> - application level
> - OS / Graphics API level
> - printer driver level
>
> The main idea og my proposal is transparency what happens in this chain
> by embedding meta-data into the print file:
> - the application creating the print data writes into the meta-data what
> the application did concerning colormanagement
> - the OS / Graphics API handling the meta-data, does the same
> - the printer driver is able to print this meta-data incl. informations
> for colormanagement on printer-driver in a control slug
>
> So by just activating the control slug, the user can easily see what
> happens in the print chain concerning colormanagement.
>
> The certification is mainly about, that the applications, the OS /
> Graphics API and the printer driver are able to handle this meta-data.
_______________________________________________
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