[Openicc] GoSoC 2011: CPD and target printing

[Chris Murphy]

On May 16, 2011, at 6:39 AM, Scott Geffert wrote:

> Applications are currently unreliable because each party has been forced to create their own workarounds to address a lack of standards when it comes to print dialogs and processing.

Applications which actually ARE specialized for the task, are currently only unreliable on one platform. It has nothing to do with lack of standards. It has everything to do with an improperly designed architecture with flawed assumptions, that's overly complicated for the level of documentation provided.

> Frankly forcing users to use special applications in order to open up certain functionality runs counter to the idea of open standards.

First of all no one is forced to use a special application. They can use whatever app they want, and it may or may not work. I am suggesting the effort should be on ensuring at least one (special) application works. If there are 99 other applications that can also print targets, that's fine. But with limited resources it does not make sense to propose all applications should be required/forced to print profile targets correctly. It's just unrealistic. And it comes with other consequences.

And if I understand correctly, it's moot because the GNOME folks have veto'd even one UI element related to color management appearing in the print dialog.

Second, target printing is a special function, and a special API and app or target encoding for that special function does NOT run counter to open standards. They're entirely unrelated issues. It's like saying forcing users to use a web browser to access web sites runs counter to the idea of open standards. It makes no sense.  My web browser doesn't open ODF docs either, I have to use TextEdit, OpenOffice or LibreOffice - something specific to the task of reading ODF.

> Imagine the cost to Adobe, Epson and other application developers to constantly chase this problem. It is in everyones best interest to move towards a more universal experience that fully supports ICC protocols.

I don't see a relationship between the problem and ICC protocols, and how this would solve the target printing problem on Mac OS.

I do see the cost factor and incentives for a solution from Adobe and Epson. But Epson is the company that keeps poking itself in the eye. They know what they're supposed to be doing with respect to their drivers, but their business structure seems to ensure key people who know these things move on, and are replaced by people who don't. So periodically you get a new driver that doesn't follow the rules, and we start getting screwed up profile targets again.


Chris Murphy