Why? Because None is chosen in Proof Output in QX7. Now if you have Quark and Photoshop open side-by-side, one can see clearly that they both look the same (showing that Quark, like Photoshop, is using the sRGB IEC61966-2.1 profile to preview the untagged RGB). Now make a new Quark 7 document, make a picture box, get picture, and link to the TEST image on your desktop.
Open an sRGB IEC61966-2.1 image in Photoshop and save a copy, with the name ending in TEST, on your desktop, and don't include the profile when saving. Quark by default is showing customers what their untagged RGB should probably likely look like (by displaying the untagged RGB with the sRGB IEC61966-2.1 profile when using the Proof Output: None, although no where in their settings do they have the sRGB IEC61966-2.1 profile, so we know it's not going to actually be used for output), but Quark is not showing the customer what it's really going to look like until ANOTHER Proof Output is chosen. If I choose Proof Output of CMYK or CMYK and Spot, THEN AND ONLY THEN do I get what color I'm really going to get.
In Quark 7's Color Manager settings, whether it is set to QuarkXPress Emulate Legacy, QuarkXPress 7.0 Default, or a custom setup, when using Proof Output None, Quark doesn't really show what I'll get from my output. If I place an untagged RGB in Quark 7 (or have one in an older legacy document I open), the default Proof Output is None. I beta tested Quark 7, let them know the issues, and they have gone through 7.0, 7.1, 7.2, and 7.3 without fixing these issues.įor instance, one issue I find egregious is the fact Quark is lying to their customers with their previews.
0 kommentar(er)
