yeah i had issues after installing - try installing the 7.3 upgrade, but enjoy the 300meg file ok.

not had many issues so far - then again i'm seeing more and more jobs in indesign now - which is so nice! we've had a couple of pdf's supplied by quack and thankfully (luckily) they were not complex with transparency and stuff

if we can, and its a big if, we now pdf out of quack and use indesign. quacks hi-res preview doesnt work for positioning our cutters and cartons nicely, so i just give up with this crap - give me whatever shitty pdf you can quack - i'll fix it and do it in indy

haa stargate i got fek all dude - shit in shit out - my motto

agfa suck!!!!!!!  fuji have better plates! apogee is shyte......

yeah we've lost a few to the chinese, and parts of europe as well

kid leo is right as well - those "must have tomorrow" turnrounds bite the dust sometimes....sucks.

if you can use illustrator to a good degree you already know a good deal of indesign - very similar in a lot of ways

ok - lets have a shot at this - since we might be searchable at some point, lets get some nuts and bolts info going

detail how best to set up colour management for a pre-press environment.

what profiles should/shouldn't be used? how to allow for dot gain? how do you profile a press? could this set up be used for ctf and ctp?

what do you do if you have more than one press and print on several substrates?

how can you apply these methods into proofing?

ahh trapping - no not the stuff of nightclubs and pubs and endless smalltalk (read bullshit) with the ladies, but that little overlap of colours to make things look pretty

well, i use a 0.2pt spread on most things, depending on its size. now thats a thing. we get pdf's supplied (packaging here), and we'll check em out then bung em into indy, apply a trap preset (that we've defined) and away we go - thing is, on smaller elements in the project, those "across the board" traps can look too heavy - but its a job by job thing and we have other methods to trap jobs

if its straight indy files we'll trap it manually in indy, and trap any placed/linked files in their native app as well

sounds long winded but it isnt - trapping is quick and easy after a bit of practise

transparency in quack is  a no brainer since the next move is postscript from your quack file. yes it can make an object "transparent" - but because you can doesnt mean you should

postscript + transparency=potential big problems - so quack doesnt truely support transparency - on an object level or one bit level

the install - well - i installed it on my ppcg5 3g rammers, silly size drive, dual 2.3ghz chippys - and had to download the 7.3 upgrade (300 meg in size) and install that as well just to get quack to boot up. then the registration/activation code shuffle dance as well and it was fun.

cs3 on the other hand, all of it, installed in about a hour tops.

 

quark sucks!