<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Or not. :)<div><br></div><div><br><div><div><div><div>On 2013-05-22, at 11:38 AM, edmund ronald <<a href="mailto:edmundronald@gmail.com">edmundronald@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">If all else fails, maybe the local CUPS web server can store and serve XML inking data and even profiles associated with a media-type keyword :)<div><br></div><div>Edmund</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, May 22, 2013 at 3:15 PM, Michael Sweet <span dir="ltr"><<a href="mailto:msweet@apple.com" target="_blank">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">Edmund,<div><br><div><div>On 2013-05-22, at 5:18 AM, edmund ronald <<a href="mailto:edmundronald@gmail.com" target="_blank">edmundronald@gmail.com</a>> wrote:</div><blockquote type="cite">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><font>...</font></div><div class="im"><div>I think this issue of making inking parameters first order citizens was discussed at length on this list - what mechanism is going to be used to allow people to load and save queue inking parameters? </div>
</div></div></div></div></blockquote><br></div><div>Yes, this issue has been discussed here, at OpenPrinting meetings, and in PWG meetings. The consensus so far is that this isn't something we can easily standardize - different drivers do things wildly differently, and what would work for Gutenprint wouldn't work for, say, the old CUPS DDK drivers.</div>
<div><br></div><div>My recommended solution is to associate linearization curves and other driver-specific data with media type and ink type names - this provides access to data that has been stored in a PPD file or other driver-specific location through a simple keyword/string (think: a preset or saved setting name), and that can subsequently be used when printing targets for profiling and (finally) printing documents using the generated profile. This is also consistent across drivers and printers.</div>
<div><br></div><div>The initial ink characterization will likely need to be done using a driver-specific utility unless the stakeholders can agree on a generic set of options that satisfy their requirements. However, I know that in the past Robert has claimed the current option/attribute support in CUPS was insufficient to supply linearization curves with a print job, so that level of integration/support may not be possible.</div>
<div class="im"><br><div>
<span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:'Andale Mono';word-spacing:0px"><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:'Andale Mono';word-spacing:0px"><div style="word-wrap:break-word">
_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></div></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></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: '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; font-size: medium; "><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; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></div></div></div></body></html>