<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hello Mike an all,<br>
There is definetely a very import use case for "embedding arbitrary
ICC device profiles into a CUPS raster stream":<br>
<br>
We need a mechanism, that the colormanagement in "..toraster" is
synchronized with the driver setup. <br>
<br>
Such workflow must include the use case, that the user can download
a printer profile and can easily configure it in his printing
environment.<br>
<br>
For this use case, the printer profile must have metadata included
to allow a synchronization with driver settings after download. The
most secure mechanism in my eyes is to embed the driver settings
directly into the profile and define a mechanism for handing over
the settings to the driver, when the profile is used.<br>
<br>
As the printer profile is applied in "..toraster", we need a
mechanism that the driver knows which profile has been used in
"..toraster" and which driver setting should be used for printing.<br>
If we embedd the printer profile from "..toraster" conversion into
the CUPS raster file, the driver simply can extract the driver
settings from the profile and use it for printing.<br>
<br>
I currently don not see an alternative approach to solve the use
case of downloading and configuring a printer profile.<br>
<br>
<br>
Best regards<br>
Jan-Peter<br>
<br>
<br>
Am 01.06.11 18:03, schrieb Michael Sweet:
<blockquote
cite="mid:5031C4BB-C5C0-4130-806C-ADF661175839@apple.com"
type="cite">
<div>
<div>On Jun 1, 2011, at 7:46 AM, Jan-Peter Homann wrote:</div>
<blockquote type="cite">
<div><font class="Apple-style-span" color="#000000">...</font></div>
</blockquote>
<blockquote type="cite">
<div>My question:<br>
How fast is it possible to extend the CUPS specifcation to
allow embedding of an ICC in CUPS-raster format like in
TIFF, JPEG or PNG ?<br>
</div>
</blockquote>
<div><br>
</div>
<div>Jan-Peter,</div>
<div><br>
</div>
It is not possible, and we will not extend CUPS raster to
support embedding of ICC profiles. CUPS Raster is a streaming
raster format to get pixels to the driver or printer - it is a
"last mile" format. There is no use case for embedding arbitrary
ICC device profiles into a CUPS raster stream since the printer
and driver are not going to do anything with the information,
they will just render the device color data provided by the
upstream *toraster filter.</div>
<div><br>
</div>
<div><br>
<blockquote type="cite">
<div><br>
Best regards<br>
Jan-Peter<br>
<br>
<br>
Am 01.06.11 15:40, schrieb Kai-Uwe Behrmann:<br>
<blockquote type="cite">On 01.06.2011 15:22, Michael Vrhel
wrote:<br>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">Hi Jan-Peter,<br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">The embedding of the data's
profile into the raster format is<br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">something that should be in place
by the next release of ghostscript<br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">in August (9.03) . I have an open
enhancement request for this for<br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">the TIFF, JPEG and PNG output
devices of ghostscript. A similar<br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">thing could be done for the CUPs
device, which I believe is the device<br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">used for gstoraster. However, I
am not familiar with where or how<br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">the data is packed into the CUPs
raster.<br>
</blockquote>
</blockquote>
<blockquote type="cite">> From Till's comments, embedding
a ICC profile into CUPS raster seems<br>
</blockquote>
<blockquote type="cite">currently not possible. Even though
I agree with Jan-Peter, that would<br>
</blockquote>
<blockquote type="cite">have been a more clever solution.<br>
</blockquote>
<blockquote type="cite"><br>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">My plan is to add in a new device
parameter that can be set on the<br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">command line to indicate if the
profile should or should not be<br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">embedded. I need to decide what
the default behavior should be (i.e.<br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">to embed or not) .<br>
</blockquote>
</blockquote>
<blockquote type="cite">Tagging/embedding is a good thing.
Otherwise the datas colour space is<br>
</blockquote>
<blockquote type="cite">not defined, which will often become
data loss. So generally speaking<br>
</blockquote>
<blockquote type="cite">embedding should be the default.<br>
</blockquote>
<blockquote type="cite"><br>
</blockquote>
<blockquote type="cite">kind regards<br>
</blockquote>
<blockquote type="cite">Kai-Uwe<br>
</blockquote>
<blockquote type="cite"><br>
</blockquote>
<br>
<br>
-- <br>
---------- Please note the new adress --------------<br>
<br>
homann colormanagement --------- fon +49 30 611 075 18<br>
Jan-Peter Homann ------------ mobile +49 171 54 70 358<br>
Cotheniusstr. 3 -------- <a moz-do-not-send="true"
href="http://www.colormanagement.de">http://www.colormanagement.de</a><br>
10407 Berlin -------- <a moz-do-not-send="true"
href="mailto:homann@colormanagement.de">mailto:homann@colormanagement.de</a><br>
<br>
<br>
</div>
</blockquote>
</div>
<br>
<div>
<span class="Apple-style-span" style="border-collapse: separate;
color: rgb(0, 0, 0); font-family: Helvetica; font-style:
normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: 2;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px; font-size: medium;">
<div>________________________________________________________________________<br>
Michael Sweet, Senior Printing System Engineer, PWG Chair<br>
</div>
</span>
</div>
<br>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
---------- Please note the new adress --------------
homann colormanagement --------- fon +49 30 611 075 18
Jan-Peter Homann ------------ mobile +49 171 54 70 358
Cotheniusstr. 3 -------- <a class="moz-txt-link-freetext" href="http://www.colormanagement.de">http://www.colormanagement.de</a>
10407 Berlin -------- <a class="moz-txt-link-freetext" href="mailto:homann@colormanagement.de">mailto:homann@colormanagement.de</a>
</pre>
</body>
</html>