To the previous person who said Quark doesn't get it... YOU don't get it! I have to deal with junk sent in by people who don't have a clue how to prepare files to be printed every day. I bet who ever gets your jobs feels the same way!
Transparency is NEVER used unflattened in print production. Quark is outputting the file correctly. All the so-called artist who insist on using layered native files don't have a clue what goes on after the printer gets the file. We flatten everything, and generally convert native files to formats like TIFF and EPS. Why? OPI that's why. Most RIPS don't know what a .PSD or .AI file is, and the RIP will abort.
Presses don't print transparency. They print a CMYK rendering of what the shade would be if it wasn't transparent. You have to flatten and raster process (RIP) that file to get there.
Transparency is more of a headache than anything else, especially with applications like Illustrator. Generally the same artist also has their transparency flattening settings to low resolution as well as their raster settings to 72 ppi! It's just a short cut for lazy people. Yes, doing it the right way often takes longer, but then the production artist at the printer wont have to mess with the stupid files all day, and the client will save a lot on pre-press time. Also, if you are printing with spot colors? Forget transparency. It doesn't work. Make a tint instead. The spot will get RIP'ed to CMYK.
InDesign is great, but Quark was smart to stay away from that junk. Do everyone a favor and create your transparencies in something like Illustrator and then *flatten the file* and save it as an EPS! Your printer will thank you, or at least not call you names behind your back.
I've been in print industry for the past 29 years, and I've seen nothing but the quality of files sent in go down the tubes. I don't know what schools are teaching (or more importantly NOT teaching) these days, but most designers don't understand printing AT ALL... most don't what a spot color is and when to use one, (or they wouldn't use 10 spots on a 4 color job) and don't realize that most RIP's cannot use native layered files. I see stupid things everyday like white set to overprint, spot colors used on CMYK jobs, CMYK used on two color spot jobs, spot "process black" used on CMYK jobs, and instead of doing a tint of a color, they drop a transparent white over it! Stupid. That's not the correct way to do things. It's a kluge! Who taught you people this junk? Go get your money back!
Luckily these days we RIP everything to PDF first (Printergy EVO or RAMpage), but the files do get flattened. Don't fool yourself. Even then there's more problems then there should be. All those transparent areas that weren't flattened often show up as white boxes.
Quark has its place in the industry, and as much as I use ID, I still prefer Quark's ways of doing things, like using picture boxes. ID is too often much like PageMaker. And when we can't get difficult ID files to print, we save the pages as EPS files and print them from Quark!
QuarkXPress
Page layout and design for print and web.
Version: 8.12
Do we REALLY want an Adobe monopoly?
Feedback Type: Commentary
Contributed by: DavidRavenMoon Friday, August 01 2008 @ 12:49 PM PDT
Product Platform: MacOSX
Used Product For: Over One Year
Recommend Product: YES
Comments
Do we REALLY want an Adobe monopoly? - DavidRavenMoon
I absolutely agree.I love Adobe stuff. Been using them since Photoshop 2.5 and Illustrator 88. I was never crazy about Pagemaker, I liked Quark much better.
Obviously everyone else did too. InDesign is great in its own way, and I use it more and more for my own work. But Quark is still a very good program. They are a little slow to implement some things, but at least they had a native OS X version first.
These are all tools. Right now I think they are in a race to see who can add more gimmicks. Do we need Quark to be able to generate web pages? I don't think so. But they have to keep up with InDesign.
Competition is a good thing. Look at what happened when Adobe bought Macromedia. A lot of people really loved Freehand, and I was a big fan of GoLive. Now I have to learn Dreamweaver. That sucks.
I guess this is progress.
Friday, August 01 2008 @ 04:35 PM PDT
Do we REALLY want an Adobe monopoly? - A. Nony Mouse
I like transparency for creation but you can't RIP with it- no biggie. Just don't make the mistake of using EPS either. That will guarantee the crash- how many times we've had to hunt down embedded EPS' in documents because they were a cause for some alarm. At least in ID you can use native files like AI for those and not worry about problems until its time to output- any preflight will catch the transparency. Heck if you have a Xinet solution in place you can do it right the first time without having to go out the of way to replace all your artwork before collection.Friday, August 01 2008 @ 05:51 PM PDT
Do we REALLY want an Adobe monopoly? - DavidRavenMoon
I've never had an issue with EPS files... but you should link them, not embed them. Some people think it's OK to copy and paste images into a document. Then that breaks the OPI links.The other issue is people don't know the correct way to save an EMP files, and they are often missing the fonts.
Adobe has made it fairly brainless to save a PDF file from ID, and that's a very good thing.
Friday, August 01 2008 @ 06:12 PM PDT
Do we REALLY want an Adobe monopoly? - W-Creative
My transparencies are just fine...PDFX-1a baby... flat, RIP-friendly, format straight from Indesign and I can use all the transparent psd and ai files I want. Get with the times man. Your point is moot.
Saturday, August 02 2008 @ 08:55 AM PDT
Do we REALLY want an Adobe monopoly? - DavidRavenMoon
Right... you said flat. The original poster was saying why does Quark make you flatten transparencies.Quark makes perfectly good PDF's also, but we use Printergy to make the PDF's, not the native app.
Saturday, August 02 2008 @ 10:50 AM PDT
Do we REALLY want an Adobe monopoly? - richard155
Transparency had been the biggest problem in pre-press for the last 5 years. Adobe creates design level applications (Illustrator and InDesign) that their RIPs can not handle. Native PSD and AI import ability is great, but until recently the majority of RIPs could not handle those features.Where I work, most of the files submitted have very few problems, however, I have twice as many problem ID files as I do QXP files, and we still see more QXP files than ID, although that is changing.
We need both programs. Instead of just comparing them they should each be judged on their own merits.
Reply to This
Friday, August 01 2008 @ 01:54 PM PDT