QuarkXPress: Color management

Re: QXP 7. Wow what a mess!

ampegg66 — Tue, 03 Jun 2008 20:50:38 GMT

I'm certainly no expert, but my understanding is that "Tint" and "Shade" are the same thing, and neither has anything to do with transparency. Opacity, on the other hand, DOES introduce transparency, which is why I avoid using Opacity unless there's a specific transparency effect I'm looking for. If you're just wanting to lighten a color, Opacity is not how I would do it.

I don't know why you'd be seeing any different effect than Quark 6 when using Shade (since there's really not an effect or any color blending, just changing the lightness/darkness of a color). Are you sure you're not just seeing the Quark 7 color management engine, which looks totally different from Quark 6? You could try setting your Color Manager preferences to "QuarkXPress Emulate Legacy" and see if that makes a difference.

Re: QXP 7. Wow what a mess!

brianahebert — Mon, 02 Jun 2008 20:28:03 GMT

Quark re-wrote it's colour engine and the pantone color book has been redefined.

QXP 7. Wow what a mess!

Baddog — Mon, 02 Jun 2008 17:41:23 GMT

Hi, we have recently had the whole network (20 users) upgraded to Q7 after waiting eagerly for around 6 months. Great I thought, now we can get on with things, but here come the problems...

We have noticed a problem (1 of many and we're only 2 weeks in) which is really worrying...when we open a legacy file with a colour tint applied in 6, the 'new' pallette changes the tint to a 'shade' of the colour which gives us a totally different effect.

Fix: Change the 'shade' to 100% and drop the 'opacity' to the same value as the original 'tint (Q6).

This is a complete nightmare as there is no way of globally changing the document without having style sheeted the whole document in Q6.

I have been a loyal supporter since the late 80's but am losing the faith real quick as each time this happens, people ask the question...why upgrade and who suggested it.