<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On May 12, 2011, at 1:14 PM, edmund ronald wrote:</div><blockquote type="cite">Which Apple application can print targets on Mac OS X? </blockquote><div><br></div>I *think* Aperture can, but that's about it for *Apple* applications. Adobe Photoshop can print targets, and most of the profiling software also has the necessary support using some rather obscure API to get the print file tagged with the right device profile so that the "identity" color path gets used (no transforms).</div><div><br></div><div>I'd like to get the necessary support for this in IPP Everywhere so that we can adopt a simpler method for doing target printing on Mac OS X - then it will just be a matter of setting a job ticket key/value pair for the existing print APIs.</div><div><br></div><div>However, I really don't see us adding support for target printing in the regular print dialog or to Preview, for example, since target printing isn't a normal user activity and needs the corresponding profiling software anyways...</div><div><br></div><div>Instead, I'd expect a user to run an application (or combination of apps in some sort of work flow) specifically geared to target generation, printing, and measurement followed by the profile generation and registration/installation. The app that prints the target can tell the printing system what it is doing (no need for the user to click yet another UI control...)</div><div><br></div><div><blockquote type="cite"><div><br></div><div>Edmund<br><br><div class="gmail_quote">On Thu, May 12, 2011 at 6:48 PM, Michael Sweet <span dir="ltr"><<a href="mailto:msweet@apple.com">msweet@apple.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style="word-wrap:break-word"><div><div>On May 12, 2011, at 7:07 AM, Kai-Uwe Behrmann wrote:</div><blockquote type="cite">
<div><blockquote type="cite"><font color="#000000">...</font></blockquote><div class="im"><blockquote type="cite">The workflow I would like to see is this:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">
1. The profiling app handles printing targets, reading targets, generating profiles, and registering profiles with their associated settings (call the combination a "preset" for lack of a better word). The same kind of application could create new presets using existing profiles (i.e. this is where you would be able to choose an alternate profile, even if it wasn't qualified for use with the settings you want...)<br>
</blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">2. The print dialog allows the user to select presets. When no preset is chosen, the print dialog will choose a profile based on the vendor rules.<br>
</blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">3. The printing system and/or color management system provide API to query and store preset information. Ideally this API allows for user, system, network, and vendor presets.<br>
</blockquote><br>2. and 3. reads good. For 1. I would prefer some more independence,<br>beside applications which want cover all in their own.<br></div></div></blockquote><div><br></div>There are very few applications that actually have everything needed to print a target and generate a profile. Even Adobe Photoshop doesn't do it. That said, I am not saying there is only one application that does #1, but that the application in #1 is distinct from a normal user application that prints (using #2).</div>
<div><br></div><div>
<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;text-align:auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><div>
________________________________________________________________________<div class="im"><br>Michael Sweet, Senior Printing System Engineer, PWG Chair<br></div></div></span>
</div>
<br></div><br>_______________________________________________<br>
openicc mailing list<br>
<a href="mailto:openicc@lists.freedesktop.org">openicc@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/openicc" target="_blank">http://lists.freedesktop.org/mailman/listinfo/openicc</a><br></blockquote></div><br></div>
_______________________________________________<br>openicc mailing list<br><a href="mailto:openicc@lists.freedesktop.org">openicc@lists.freedesktop.org</a><br>http://lists.freedesktop.org/mailman/listinfo/openicc</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-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, Senior Printing System Engineer, PWG Chair<br></div></span>
</div>
<br></body></html>