What a delightful idea! The profile can be selected if it is fuzzily relevant to inking and media settings, inking can be selected if it is fuzzily relevant to media settings, etc etc. <br><div class="gmail_quote">I'm all for it providing you write the fuzzy matching code :)</div> <div class="gmail_quote"><br></div><div class="gmail_quote">Edmund</div><div class="gmail_quote"><br></div><div class="gmail_quote">On Wed, Jan 19, 2011 at 12:45 AM, Ann L McCarthy <span dir="ltr"><<a href="mailto:almccart@lexmark.com">almccart@lexmark.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <br><font size="2" face="sans-serif">Yes, you would not want to indicate a single specific set of driver setting values when the profile could be used for several settings values. </font> <br><font size="2" face="sans-serif">However, it also could be possible to define the metadata to handle 'this profile is used for X range of values of paramter Y, and so on.</font> <br><font size="2" face="sans-serif">That way the output profile is not modified -- rather it can be selected for a particular set of driver setting values by comparing the single current value to the range of values the profile covers for each setting.</font> <br><div class="im"> <br><font size="2" face="sans-serif">Best regards,<br> Ann McCarthy<br> Imaging Systems R&D<br> Lexmark International, Inc.<br> <br> <br> </font> <br> <br> <br> </div><p></p><table width="100%"> <tbody><tr valign="top"> <td width="40%"><div class="im"><font size="1" face="sans-serif"><b>Graeme Gill <<a href="mailto:graeme@argyllcms.com" target="_blank">graeme@argyllcms.com</a>></b> </font> <br></div><div class="im"><font size="1" face="sans-serif">Sent by: openicc-bounces+almccart=<a href="http://lexmark.com" target="_blank">lexmark.com</a>@<a href="http://lists.freedesktop.org" target="_blank">lists.freedesktop.org</a></font> </div><p><font size="1" face="sans-serif">01/18/2011 06:16 PM</font> </p></td><td width="59%"> <table width="100%"> <tbody><tr valign="top"> <td> <div align="right"><font size="1" face="sans-serif">To</font></div> </td><td><div class="im"><font size="1" face="sans-serif">OpenICC Liste <<a href="mailto:openicc@lists.freedesktop.org" target="_blank">openicc@lists.freedesktop.org</a>></font> </div></td></tr><tr valign="top"> <td> <div align="right"><font size="1" face="sans-serif">cc</font></div> </td><td> </td></tr><tr valign="top"> <td> <div align="right"><font size="1" face="sans-serif">Subject</font></div> </td><td><font size="1" face="sans-serif">Re: [Openicc] Assigning icc profiles to driver settings</font></td></tr></tbody></table> <br> <table> <tbody><tr valign="top"> <td> </td><td></td></tr></tbody></table> <br></td></tr></tbody></table> <br> <br><div><div></div><div class="h5"> <br><tt><font size="2">Leonard Rosenthol wrote:<br> > On Tue, Jan 18, 2011 at 11:26 AM, Jan-Peter Homann<<br> > <a href="mailto:homann@colormanagement.de" target="_blank">homann@colormanagement.de</a>> wrote:<br> ><br> >> 1) PPD colour keywords:<br> >> The PPD for a given printer must be able, to describe all color relevant<br> >> driver settings with all parameters (incl. low level driver settings if<br> >> necessary)<br> >> an ICC profile will be assigned to a proper parametrized PPD and the PPD<br> >> will completely set up the color options in the printer driver.<br> >><br> >><br> > I (and other folks at Adobe) support thsi model. In fact, we've been trying<br> > to convince various printer vendors to do this for their PPDs for YEARS.<br> <br> This is only a good approach for PS based front ends to the printer, where<br> a PPD parser is readily available. It is less desirable for other, simpler<br> front ends (ie. a direct raster print pipe).<br> <br> > However, all of the major vendors are unwilling to do so for various<br> > business and/or technical reasons. So any provided PPDs would need to be<br> > MODIFIED versions of the originals...<br> ><br> >> 2) Driver settings implemented as metadata-information into the ICC-profile<br> >> Like with the PPD-workflow, all color relebant printer driver settings are<br> >> stored as metadata into the ICC-profile.<br> ><br> > Modification of ICC profiles is a BAD IDEA!<br> ><br> > As noted elsewhere in the thread, it breaks the ID and prevent the use of<br> > the profiles in other workflows where comparison of profiles is important.<br> <br> Another disadvantage of this approach is that it makes it hard to<br> re-use profiles for similar but slightly different printer set-ups.<br> <br> One of the practical issues is that there is a combinatorial<br> explosion of printer settings, so it's impossible to profile<br> all possible combinations. One of the advantages of separating<br> calibration from profiling is that it's possible to<br> mix and match for good (but not perfect) color. This involves<br> using profiles for set-ups other than the one they were created for.<br> <br> For instance, changing the screen pattern or DPI often changes<br> the response transfer curve, but it's feasible to calibrate<br> for many of these combinations, and then mix it with<br> a profile that has been made for that paper & ink combination,<br> yielding quite reasonable results.<br> <br> Graeme Gill.<br> <br> <br> _______________________________________________<br> openicc mailing list<br> <a href="mailto:openicc@lists.freedesktop.org" target="_blank">openicc@lists.freedesktop.org</a><br> </font></tt><a href="http://lists.freedesktop.org/mailman/listinfo/openicc" target="_blank"><tt><font size="2">http://lists.freedesktop.org/mailman/listinfo/openicc<br> </font></tt></a> <br></div></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>