[Printing-architecture] [Gimp-print-devel] [Openicc] Colour
lists at colorremedies.com
Sun Nov 15 11:32:32 PST 2009
On Nov 14, 2009, at 3:59 PM, Michael Sweet wrote:
> On Nov 14, 2009, at 2:10 AM, Chris Murphy wrote:
>> Michael, yes, I have no doubt about that. The problem is that these sorts of color problems with printing are recurring themes. Epson is not the only one who has had problems, although they very well may be the worst offender. But we don't have these kinds of problems on Windows. That should be a WTF moment for Apple. Sane people have started to wonder, rationally, if there is something fwrong with the architecture when there are so many recurring problems of this sort, through multiple major revisions of the operating system. We've experienced color related problems with Tioga drivers too.
> Windows doesn't provide the same level of support for color as Mac OS X, and to say that Windows doesn't have these problems is a lie - they are just hidden from most users since there isn't a "use this profile" option staring you in the face every time you print.
> In any case, venting here won't fix things in Mac OS X. Please file bugs with Apple so that any issues get escalated and dealt with:
A lie? As in, an intentionally false statement? That's an interesting assertion. I know for a fact it's possible to print profile targets reliably on Windows. There are other problems on Windows, but reliably printing profile targets and prematching color without ICM becoming involved is not one of them, because it is not aggressively invasive like ColorSync. Those are the problems I'm referring to.
My entrance to the thread was to lend my perspective to Linux dvelopers on avoiding what I consider to be major flaws with printing and color on OS X. Subsequent posts have been responses. These are not new complaints. Multiple forums including Apple's ColorSync User's list and support forums are littered with such complaints.
There isn't a mechanism for relaying perceived (or real) architectural flaws with Apple. Doing so on bug reporter consistently yields "works as intended" responses from engineering. I know because I've been down that road already.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Printing-architecture