<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 2, 2011, at 5:47 PM, Hal V. Engel wrote:</div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Verdana; 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; -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 style="font-family: 'DejaVu Sans'; font-size: 12pt; font-weight: 400; font-style: normal; "><font class="Apple-style-span" color="#000000" face="Verdana"><span class="Apple-style-span" style="font-size: medium;"><br></span></font><div style="white-space: pre-wrap; margin-top: 0px; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; text-indent: 0px; ">> Should these applications be able to sent a "token" with their print job</div><div style="white-space: pre-wrap; margin-top: 0px; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; text-indent: 0px; ">> that automatically sets the CPD to "no color management" automatically to</div><div style="white-space: pre-wrap; margin-top: 0px; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; text-indent: 0px; ">> prevent a default condition of double color management?</div><div style="white-space: pre-wrap; margin-top: 0px; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; text-indent: 0px; "><br></div><div style="white-space: pre-wrap; margin-top: 0px; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; text-indent: 0px; ">That is a possibiliy but why not just tag the objects in the PDF file correctly so that it is passed through?</div></div></span></blockquote><div><br></div><div>The PDF is not yet generated at the time the CPD is presented to the user, nor is the job ticket. So a "token" is needed to the CPD at the time it's called. Similar to the document preview information. </div><div><br></div><div>When I hit "Print" in the application, that app presumably sends some information to cause the CPD to be brought up, including number of pages, document orientation, preview, and if the application is going to prematch the print job. If it is, then I think the CPD color management options should snap automatically to "Application Manages Color". I am disinclined to suggest that the user would be enabled to change this pop-up menu, that it should lock to this setting, or they need to go back to the app and change settings there if they want specific control in the CPD.</div><div><br></div><div>If application prematching is used, yes the PDF would be properly formed: something like PDF/X-4 but all objects would be /Device based with an OutputIntent should convey to the pipeline that the PDF should not be touched any further. But would still allow live transparency so Ghostscript can produce a better result for actual output device resolution than the application can.</div><div><br></div><div>There is little distinction between the PDF spool from a prematching application, and one that wants color management off for the purpose of calibration or characterization.</div><div><br></div><div><br></div><div><br></div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Verdana; 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; -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 style="font-family: 'DejaVu Sans'; font-size: 12pt; font-weight: 400; font-style: normal; "><div style="white-space: pre-wrap; margin-top: 0px; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; text-indent: 0px; ">The only time pass through or not is ambiguous is when there is no OutputIntent and the objects are tagged as DeviceXXX and there is only one DeviceXXX type used and it matches the printer color mode.</div></div></span></blockquote><div><br></div><div>Agreed. This is ambiguous.</div><br><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Verdana; 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; -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 style="font-family: 'DejaVu Sans'; font-size: 12pt; font-weight: 400; font-style: normal; "><div style="white-space: pre-wrap; margin-top: 0px; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; text-indent: 0px; "> A CM aware app wanting it's already CMed spool file to pass through should set the profiles of the embedded objects == the OutputIntent and it will get pass through since this is completely unambiguous. The main thing is to make sure that pdftoraster honors OutputIntent.</div></div></span></blockquote><div><br></div><div>Yes.</div><div><br></div></div><br><div>Chris Murphy</div></body></html>