(damn Microsoft top posting fixed)
Mary Sauer said:
When you create a PostScript file in Publisher you have to send the host
fonts,
this is why in printer properties you turn off the option "Do not send fonts
to
Distiller". Every .ps file I have converted has open correctly with Acrobat.
Yes, it opens correctly with Acrobat. That's fine. And if the person
who opens the PDF has the same license-restricted TrueType fonts on his
host system as what were used to create the PDF, he can print the PDF as
well.
But if he doesn't have the fonts, printing will fail.
If the document creator gives it to a commercial printer who wants to
import the PDF directly into his workflow, it will also fail--because
his workflow expects the PDF to be completely self-contained. Best
case, his PDF workflow includes a mechanism to look for the fonts on the
commercial printer's system--but if the commercial printer doesn't own
the TrueType fonts in question, it'll fail.
Don't confuse opening a PDF with being able to use it in a commercial
printing workflow.
I
am assuming the recipients are opening the PostScript file with Acrobat.
Read the original post--he's creating PDF himself and sending it out,
and the printer he's sending it to can't use it.
Real publishing programs have a mechanism for turning type to outlines.
Publisher doesn't. He's stuck. There are many solutions to this, but
we'd have to know the commercial printer's workflow. The printer
himself gave one option that would solve the problem for free: turn
type to outlines. Gee, if only he could.
Otherwise John will have to save the file as a picture and send it along that
way.
Publisher must die, if this is the only solution you can come up with.
Everyone, repeat after me: Publisher is for creating flyers that you
print at home on your inkjet printer. Publisher is not for creating
anything that's going to a commercial printer of any kind.
By the way--I'm an Adobe Certified Expert for Acrobat. Do you want to
discuss PDF workflows?