RE: Save as PDF vs Print to PS and then Distill

[Dov Isaacs <isaacs@xxxxxxxxx>]

At 5/19/99 11:50 AM , Snavely, Deborah wrote:
><snip>... I suspect that the Win/Frame "Save as PDF" operation is roughly equivalent
>to using the Mac Acrobat (virtual) print driver called "PDFwriter", which
>generates quick-and-dirty PDF from just about any application but does NOT
>retain graphic quality for EPS or generate good fonts. (It did save problems
>when a particular legacy document included a page whose graphics simply
>WOULD not distill; for such, I created a PDF of the rest of the book in two
>chunks by the preferred method, then inserted one crummy-but-readable page
>of the problem page using PDFwriter because the document's source graphics
>were no longer available.)
>
>For any platform, using any source software, the good method of getting a
>file into PDF is to put everything you need (including fonts and hyperlinks)
>into the cleanest PostScript file you can generate using an Acrobat-specific
>driver and then Distill. Simple, but it takes a little explaining. 
>
>For Frame, this means we need an RFE that recommends deleting the "Save as
>PDF" function or re-naming it "Save as DRAFT PDF".
>
>Deborah Snavley

No, that isn't quite true. The "save as PDF" is actually an
often mis-wired attempt at generating PostScript and force
feeding it into the Distiller. The implementation was the problem.
In some circumstances you can get it to work, others not!

	- Dov

** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **