Re: Re. inkjets: An open letter to Tom Lianza and Lars Borg
Re: Re. inkjets: An open letter to Tom Lianza and Lars Borg
- Subject: Re: Re. inkjets: An open letter to Tom Lianza and Lars Borg
- From: Jan-Peter Homann <email@hidden>
- Date: Tue, 20 May 2008 11:30:21 +0200
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.
This is the core idea of my last letter.
An additional idea is the place for the management of
- printer profiles for different media / driver settings,
- the driver settings itself and t
- he place where the colormanagement for the print chain happens.
The association of printer profiles and printer driver settings should
be done at the printer driver and not in the OS and not at application
level.
The vendor should have the possibility to deliver standard profiles for
his standard settings and the user should be able to print without any
colormanagement for a given setting and to attach his own profile to a
setting if he wants.
If an application does the colormanagement for the print chain by
itself, the application should be able to read out the profile currently
valid for a printer driver setting and deliver colormanagement print
data wich MUST NOT further be color managed by the OS/Graphics API or
the printer driver.
Such functionality could in general be certified and in daily practice
be controlled via the meta-data in the control slug on the print-out.
Regards
Jan-Peter
Lars Borg wrote:
Jan-Peter,
Let's uplevel. You're assuming a certification process would solve the
problem in the field. Would it? I don't think so.
A certification process would only tell us it is possible to get
correct output, not that we're getting correct output right now.
A certification process doesn't verify that Joe's system is correct
right now. Maybe his paper is too moist, or an ink nozzle is
performing below par.
It seems the user needs something that can verify the system live,
including hardware deviations.
As far as I understand, this is one of the major problems.
Lars
--
*********** Neue Adresse / new adress ************
homann colormanagement ------ fon/fax +49 30 611 075 18
Jan-Peter Homann ------------- mobile +49 171 54 70 358
Christinenstr. 21 ------ http://www.colormanagement.de
10119 Berlin -------- mailto:email@hidden
*********** Neue Adresse / new adress ************
_______________________________________________
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