<div>Hello Kai-Uwe,</div><div><br></div> I agree with the idea of making everybody happy by preserving their favorite workflow :)<div> However I do think that code-sharing should be enforced to be sure that all the methods produce identical prints. </div> <div><br></div><div> For me:</div><div> - Command-line printing is super-useful once a workflow is tuned and identical conditions need to be enforced.</div><div> - GUI is very useful to lay out targets, and if necessary superimpose reference marks on them, eg. the Barbieri marks that allow the scanning spectro to find the patches. </div> <div><br><div><div class="gmail_quote">Edmund</div><div class="gmail_quote"><br></div><div class="gmail_quote"><br></div><div class="gmail_quote">On Thu, May 5, 2011 at 10:28 PM, Kai-Uwe Behrmann <span dir="ltr"><<a href="mailto:ku.b@gmx.de">ku.b@gmx.de</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hello Alastair,<br> <br> Am 05.05.11, 20:24 +0100 schrieb Alastair M. Robinson:<div class="im"><br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> On 05/05/11 16:32, Chris Murphy wrote:<br> <br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> If a single application cannot be produced to do this correctly and<br> reliably, we certainly have the very same problem with it in a CPD that<br> then all applications are subject to with no other (simple) means of<br> working around it. I think that's a problem.<br> </blockquote> <br> What strikes me is that if it's impossible to do pass-through-colour using the CPD then our standalone target-printing application has to bypass the CPD completely.<br> </blockquote> <br></div> Oh, thats not our goal. In the scheme diagram [1] is shown how to get pass through with CPD following the PDF/X standard.<br> PDF objects can only be tagged with ICC profiles if no prematched data, this means a PDF without OutputIntent, is obtained.<br> By CPD honouring a OutputIntent it is easily possible to print without altering any colour profiles in the PDF. Then DeviceXXX will be preserved.<br> <br> What would be possible by this scheme:<br> * cli tool to generate a finalised target PDF which prints in passthrough<br> mode<br> * cli tool to convert a input image into a finalised target PDF<br> * a finalised target PDF is printed on the command line<br> * a finalised target PDF is sent to CPD<br> * the finalised target is created in a GUI app and printed to CUPS<br> * the finalised target is created in a GUI app and sent to CPD<br> <br> I hope for all cli and GUI fans is some combination at least possible. It will not necessarily mean we have Linux converted instantly and osX and Windows too.<br> <br> As we are in the GSoC thread, I would wish Joseph comes to a working set of command line tools. If a GUI could be updated to use the scheme that would be great. But lets see how trivial or complicated the project will be. Polishing for robustness is more vital than bells and whistles in the first place.<div class="im"> <br> <br> <br> kind regards<br> Kai-Uwe Behrmann<br> -- <br> developing for colour management <a href="http://www.behrmann.name" target="_blank">www.behrmann.name</a> + <a href="http://www.oyranos.org" target="_blank">www.oyranos.org</a><br> <br></div> [1] <a href="http://www.oyranos.org/wiki/index.php?title=Device_Settings#CUPS" target="_blank">http://www.oyranos.org/wiki/index.php?title=Device_Settings#CUPS</a><div><div></div><div class="h5"><br> _______________________________________________<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><br> </div></div></blockquote></div><br></div></div>