Chris, speaking of hammers, a comment on my usecases of Linux printing earlier on the list would be appreciated. <div><br></div><div>Edmund<br><br><div class="gmail_quote">On Wed, Feb 29, 2012 at 1:37 AM, Chris Murphy <span dir="ltr"><<a href="mailto:lists@colorremedies.com">lists@colorremedies.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br> On Feb 28, 2012, at 3:57 PM, Graeme Gill wrote:<br> <br> > Chris Murphy wrote:<br> >> To modify the RIP behavior means everyone else that came before the RIP means everyone else<br> >> before the RIP has abandoned their responsibility, and competency.<br> ><br> > I don't agree. Fixing it at this point is a last resort, and is not something<br> > you would want to do - you have to go out of your way. But being able to<br> > fix it is a very good thing. I don't want to be held hostage by other<br> > people battles over incompetence and color management philosophy, something<br> > that (as a user) I typically have no control over.<br> <br> </div>Nope. There are a number of tools that are specifically designed to fix this problem. Professionals use professional software, and this is in any number of pre-press capable applications on the market. Brute force hammers like this one in a RIP have a tendency to be turned on and left on. The problem is the file, not the RIP's interpretation of the file.<br> <font color="#888888"><br> <br> Chris Murphy<br> </font><div><div></div><div class="h5">_______________________________________________<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> </div></div></blockquote></div><br></div>