Font Issues when printing. Quark 6.5

artpear

Member
When placing some PDF in Quark 6.5 document and printing, I sometimes get this message...

" Some EPS/PDF pictures in this document use screen fonts not available in your system, including: MyriadPro-Bold-Identity-H, etc "

I tried using a newer PPD, AdobePDF 8.0 but I get the same result

I am new at creating Press ready PDF (converting from a TIFF-IT workflow)

Is it safe to generate a PDF when you get that message or how can i fix that problem ?????

I'm desperate and lost... lol

Also, I'm using Badia Exportools in Quark 6.5 to generate single page postcript files that i then drop in Distiller 8.1 using PDF/X-1a:2001 settings, is it a safe way to do it ???

Thanks
Art
 
Last edited:
My first step would be to go back and try and find where in the linked files they might be, and rectify their font status.
This could be a tedious process, but depends on the size of your doc. [page count, number of links]. Be especially aware of possible problems with CID/Identity-H fonts. They seem to cause more than their share.

Can't comment on your Export route, as I haven't used that one specifically. Don Isbell posted a great PostScript for Later Distilling method here some months back, but I've lost track of it since. Someone may be able to post a link to it.
 
I think the Don Isbell post referred to by frailer may be the second post in this thread, specifically for Quark 7:

http://printplanet.com/forums/quark/13266-pdf-eps-quark7/2

Al

Edit: A similar method (via postscript) can be used for Q 6.5, but it involves printing with Adobe PDF (or a newer version), or Jaws PDF Creator, or SSiColor ppd used as the ppd in the setup tab of the Print dialog, and selecting "Save PDF as postscript" in the printer area (Printer Button). ***Do NOT*** use "Save as PDF" with any of these ppds because this will then use the Mac OS X Quatz Context and does not process fonts correctly!

In addition, a direct pdf export also works well for me, if the correct job options are chosen ***AND*** a virtual printer is set up ahead of time as the default printer using one of the above mentioned ppds.

Note that all my comments in this post are for Mac OS X 10.4.11.

Edit 2: I have been puzzling over the method described by Don in that thread wondering how he got Quark to export postscript instead of pdf, and I finally noticed that had written:

"Set Quark 7 preferences > PDF to make PostScript for later Distilling. Choose the 'In' folder of your Distiller Watched folder."

So I am coming back to point out that the same thing can be done in Q 6.5. But I want to re emphasize the need to set up a virtual printer ahead of time as the default printer using one of the above mentioned ppds. Which leaves me wondering if not doing this would be the reason for Don eschewing the direct export method.
 
Last edited:
The problem with using File-Export-Export page as PDF is that the only way to do single page PDF is to do them one at a time which is very time consuming.

Right now I'm testing Badia Export Tools which creates single page PDF from a multi page doc.

Where can I get a good PPD ?

Also, I sometimes have issues (CID Identity-H) from ads received from clients, Quark gives me a warning. What can I do?

Art
 
Where can I get a good PPD ?

How about one of the Adobe PDFs that are installed with versions of Acrobat Pro? Or the Jaws PDF Creator PPD installed with Quark since Q 6, or earlier. That one worked every time I tested it, but I use the ssicolor.ppd that came with Preps.

Al
 
PDF export works with Quark 6.5 AND 7 (8 too?)

PDF export works with Quark 6.5 AND 7 (8 too?)

Al,

Sorry I haven't posted back sooner. I don't actually receive the forum mail any more, I just check back occasionally to see what's going on. The PDF (actually PS) export works for both Quark 6 and Quark 7. May work for other versions too, although I haven't tried it.

The reason I do it this way is because Distiller will make a PDF out of the PS, and I know Adobe does good (better than trying to figure out Quark, and is better than Quark in tests I've done) with compression and downsampling - so I say leave it to the pros and only let Quark do what it must do.

Also, I can basically click to export PDF, choose by settings file, and click OK. If Acrobat Distiller is started, it picks up the PS and makes a PDF. So much faster than setting up the print dialog box that you have to do using any other method. I basically always use .25" for bleed (so get bleed if built into file, or if I fixed bleed, or added 1/8" fold marks outside 1/8" bleeds, it will show up in PDF), with 12pt marks offset, centering the page in that area (so that there is .5" all the way around the trim for bleeds and marks on EVERY PAGE I EVER PROCESS). So in Preps when imposing the Links (lores FPO of Page) from Nexus, I center the page in the template window made for it, bleeds are kept, and marks are masked off. Easy cheesy. Can't get better than that IMO unless completely automating.

The only thing that you need to know is that PMS colors that are spec'd as Spot inside Quark will go to CMYK PANTONE numbers, while PMS colors spec'd as Spot outside of Quark will stay Spot in the PDF. This is no problem since the alternate colorspace in the PDF for the Spot is CMYK (as long as options when exporting are set to CMYK or CMYK and Spot, and NOT As Is). So in my rip, I convert the Spot colors to CMYK if I want an all CMYK job.

Also, if using transparency, Quark doesn't let you export any live transparency out of Quark via PDF 1.4 or higher, so basically all transparency flattening must be done while outputting from Quark. This one thing alone makes Quark's days numbered. Prepress has to have a PDF that can be altered at last minute. Anything and everything in it needs to be able to be changed by prepress. Quark not seeing this is hurting us and them.

I've tried to reason with them on a number of occassions, but it's like talking to a brick wall.

Tech support nor anybody there seems to understand the simple fact that:
By default Quark 7 (both in beta and ever since, although I talked about this while 7 was still in beta) Preview is set to None, so linked RGB that has no profile is shown in appearance as if it was using sRGB IEC61966-2.1 profile (which it should be using and anyone would assume it is using sRGB profile as source for conversion to CMYK by looking at appearance when Preview set to None). In truth, as can be seen by changing Preview to CMYK or CMYK and Spot, or outputting, Quark actually uses it's default Quark 7 profile (which is the same as Adobe RGB (1998)) as source for conversion to CMYK for linked RGB that has no ICC profile. So Quark's Preview lies by default. Therefore people's faces come out looking sunburned in this situation. Does Quark care? If they did, wouldn't they have changed this awful behavior by now? Remember, I said something to them about this while 7 was still in beta, and they still DON'T GET IT! They are clueless. Therefore, I say if at all possible, use InDesign. If you can't, only let Quark take care of what it has to, and no more.

Another example of their ignorance:
PANTONE library in Quark 6.5 and Quark 7 have the exact same name, but different CMYK values. Open a Quark 6.5 in 7, and not only type wrap issues, but also CMYK PANTONE simulation issues. F'd up as a football bat.

Why can't they make it so where when opening an old file, that we can actually have it open and look like it did in the old Quark? InDesign CS3 I've had VERY few issues when doing this myself. PPC Macs that can run Quark 6.5, and Rosetta on Intel Macs that can run Quark 6.5 (I think), will not be around forever. Quark REALLY needs to come up with a plan on how all of us can open old documents in most recent Quark version on Intel Macs and NOT have these problems. Am I holding by breath? No.

Hope this helps.

Don
 
   
Back
Top