[Openicc] cupsICC on remote CUPS servers Part 2
homann at colormanagement.de
Fri May 20 09:07:57 PDT 2011
Hello Mike and all,
Your described workflow for Mac OS X hase from my point of view
following problems in an remote server envirronment:
- If printer profiles associated to a driver setting are new installed
or updated, they have to be updated on every client.
- for me, it is still unclear under Mac OSX, how the connection between
a printer profile and a driver setting is automatically maintained under
Mac OS X. If new profiles (associated with a driver setting) are
installed at the client side, we have currently no mechanism (profile
meta data) to synchronize the usage of the profile and selection of the
- It is still unclear for the enduser under Mac OS X, how rendering
intents are handled and blackpoint compensation could be activated.
Am 20.05.11 17:21, schrieb Michael Sweet:
> On May 20, 2011, at 1:14 AM, Jan-Peter Homann wrote:
>> - Is this is workflow-proposal, which makes sense for a color managed
>> print path with remote CUPS servers from your point of view ?
> On Mac OS X we actually embed the destination color profile in the PDF
> file's output intent to ensure that the server a) has the profile
> (which may be a locally-installed/registered color profile...) and b)
> uses the correct profile (rather than only the auto-selected one).
> However, that does not address the "print from the command-line" use
> case - right now we always use the default profile for the selected
> options when printing on the server.
> Michael Sweet, Easy Software Products
---------- Please note the new adress --------------
homann colormanagement --------- fon +49 30 611 075 18
Jan-Peter Homann ------------ mobile +49 171 54 70 358
Cotheniusstr. 3 -------- http://www.colormanagement.de
10407 Berlin -------- mailto:homann at colormanagement.de
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openicc