attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Daniel,<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 31, 2015, at 11:12 PM, Manchala, Daniel <<a href="mailto:Daniel.Manchala@xerox.com" class="">Daniel.Manchala@xerox.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" class="">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)" class="">
<style class=""><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div lang="EN-US" link="blue" vlink="purple" class="">
<div class="WordSection1"><p class="MsoNormal">At one of our last PWG-IPP meetings, we discussed printer-icc-profiles, and how a particular icc profile can be picked up at the printer. <o:p class=""></o:p></p><p class="MsoNormal"><o:p class=""> </o:p></p><p class="MsoNormal">Based on the spec, <o:p class=""></o:p></p><p class="MsoNormal"><span style="" class="">“5.6.30 printer-icc-profiles (1setOf collection) The RECOMMENDED "printer-icc-profiles" Printer attribute lists one or more ICC profiles that characterize the Printer or its rendering. Each collection value consists
of "profile-name (name(MAX))" and "profile-uri (uri)" member attributes plus any Job Template attributes (as member attributes) that contribute to the selection of the profile.”<o:p class=""></o:p></span></p><p class="MsoNormal"><o:p class=""> </o:p></p><p class="MsoNormal">relevant JT attributes sent from the Client match those on the Printer Description attribute and a certain icc profile will get selected.<o:p class=""></o:p></p><p class="MsoNormal"><o:p class=""> </o:p></p><p class="MsoNormal">We also discussed that it is not recommended to use/send a particular icc profile (the client selecting one of the printer-icc-profiles provided in the Get-Printer-Attributes response) in a Print-Job or Create-Job. Can you explain why this
is not recommended, but rather have a workflow wherein when the printer receives a certain JT attribute (say media-type), that particular attribute is used to look for another attribute (such as printer-icc-profile)?</p></div></div></div></blockquote><div><br class=""></div></div><div class="">ICC profiles are specific to combinations of other settings - media type, resolution, color mode/marking supplies, etc. - and generally don't work for other kinds of media, resolutions, etc.</div><div class=""><br class=""></div><div class="">One of the most common problems in current user interfaces is that they allow the user to choose both the color profile and the other settings independently. Naturally this leads to inconsistent or dramatically wrong output, ultimately yielding complaints from so-called "experts" that some combination of settings is not working for them and their workflow.</div><div class=""><br class=""></div><div class="">The primary goals of the printer-icc-profiles attribute are:</div><div class=""><br class=""></div><div class="">1. To allow administrators and operators to create and manage ICC profiles for the media and other settings used for a given printer (a print shop);</div><div class=""><br class=""></div><div class="">2. To allow ordinary users to get the best quality output without being a color expert (automatic color profile selection by the printer); and</div><div class=""><br class=""></div><div class="">3. To allow expert users to soft-proof output prior to printing.</div><div class=""><br class=""></div><div class="">*If* a Client implementation wants to include a user interface element for selecting an ICC profile, the "printer-icc-profiles" attribute provides the necessary contextual information for it to have such a selection also override the other user interface elements as needed (media type, etc.) Similarly, if the user change the value of an overridden element, the user interface can change the selected profile and/or show an alert explaining the issue and giving the user a choice (constraints). The actual profile selection is still done on the printer.</div><div class=""><br class=""></div><div class="">A Client sending a PDF document can also embed one of the ICC profiles and do the color transforms locally - the Printer, after performing its own profile selection, will then do the right thing (pass through the Device N colors since the profiles match or do a device-link transform for the actual profile used for printing) and produce consistent output every time.</div><div class=""><br class=""></div><div class="">In short, the current ICC profile support is design to minimize the number of bullets that are available to shoot oneself in the foot.</div><div class=""><br class=""></div><div class="">
<span class="Apple-style-span" style="border-collapse: separate; font-family: 'Andale Mono'; border-spacing: 0px;"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-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; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; " class="">_________________________________________________________<br class="">Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br class=""></div></body></html>