Michael,<div><br></div><div> *How* does CUPS on non-mac systems know about ICC profiles? </div><div> I have found your very clear and informative post here <a href="http://lists.freedesktop.org/archives/openicc/2005q2/000208.html">http://lists.freedesktop.org/archives/openicc/2005q2/000208.html</a></div>
<div>which indicates that the *cupsiccprofile keyword in the PPD is the appropriate declaration on the Mac. Is this now generally supported? </div><div> Also, do non-mac distribs now have a filter called up by CUPS which then does the appropriate profile conversion?</div>
<div><br></div><div>Edmund</div><div><br></div><div><div class="gmail_quote">On Sun, Jan 29, 2012 at 4:51 AM, 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">Edmund,<div><br></div><div>CUPS knows about ICC profiles, in as much as the filters support them and cupsd registers the ones listed in the PPD file, but it doesn't know about the calibration data used internally by the driver.</div>
<div><br></div><div>So if you want access to the levels/curves in Gutenprint (say, to use a custom set of dither parameters for a particular media type) then you'll need to pull the XML data from the profile used.</div>
<div><br></div><div><br></div><div><div><div><div class="h5"><div>On Jan 28, 2012, at 1:17 PM, edmund ronald wrote:</div><br></div></div><blockquote type="cite"><div><div class="h5">Richard, <div><br></div><div> I think the profile stuff happens in CUPS upstream from Gutenprint - this is a raster driver which doesn't know about colorspaces. So Gutenprint won't be reading profiles. Robert may have something different to say. </div>
<div><br></div><div> My belief, confirmed by today's phone conversations is that CUPS knows a lot about profiles though, and performs profile conversions on input data when asked nicely. </div><div><br></div><div> More pertinently , if Gutenprint writes XML (dumps its presets), it is probably being called to print a target which means that the image is DeviceRGB o DeviceCMYK -no input profilein sight and indeed none available yet. </div>
<div><br></div><div> Of course you could want Gutenprint to embed the written XML in some available profile, but that is a long time after the print has dried and been measured, so you have no reason to print again, so why ask Gutenprint? </div>
<div><br></div><div>Edmund</div><div><br><br><div class="gmail_quote">On Sat, Jan 28, 2012 at 10:04 PM, Richard Hughes <span dir="ltr"><<a href="mailto:hughsient@gmail.com" target="_blank">hughsient@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On 28 January 2012 19:56, edmund ronald <<a href="mailto:edmundronald@gmail.com" target="_blank">edmundronald@gmail.com</a>> wrote:<br>
> So, my suggestion would be that you write the code to embed and to unembed<br>
> the XML in profiles, and you task us structure the XML itself in ways which<br>
> would help you, but let us momentarily define a way we can work now with<br>
> "naked" XML and no superstructure when no profiles are involved.<br>
<br>
</div>Sounds like a fair deal. Do you want a library to use, or just provide<br>
a couple of lcms2 example snippets that can be licenced as<br>
BSD/GPL/whatever for copy/pasting? Maybe a command line utility might<br>
be easier. The cd-fix-profile utility already allows you to add random<br>
metadata to profiles, although a simpler utility might be better. Let<br>
me know what you would prefer.<br>
<span><font color="#888888"><br>
Richard.<br>
</font></span></blockquote></div><br></div></div></div><div class="im">
_______________________________________________<br>openicc mailing list<br><a href="mailto:openicc@lists.freedesktop.org" target="_blank">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></div>
</blockquote></div><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><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>