<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On May 20, 2011, at 1:14 AM, Jan-Peter Homann wrote:</div><blockquote type="cite"><div bgcolor="#ffffff" text="#000000"><font class="Apple-style-span" color="#000000">...</font></div></blockquote><blockquote type="cite"><div bgcolor="#ffffff" text="#000000">- Is this is workflow-proposal, which makes sense for a color managed print path with remote CUPS servers from your point of view ?<br></div></blockquote><div><br></div>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).</div><div><br></div><div>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.</div><div><br></div><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-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>________________________________________<br>Michael Sweet, Easy Software Products</div></span> </div> <br></body></html>