Re: Eunuchs PostScript (Was: Distiller Trivia)

[Dov Isaacs <isaacs@xxxxxxxxx>]

Thomas,

The PostScript generated by FrameMaker under UNIX is quite "bland"
and I doubt whether there is anything in it that would cause any
problems with distillation. It is exceptionally generic, circa 1990
or so.

The problems encountered by Windows and Mac users when creating PDF
from FrameMaker are associated with the (1) the problematic "save as PDF"
feature (already discussed to death here) and (2) attempts to generate
PostScript for distillation via or with cockamamie, convoluted methods 
and/or options instead of the one, simple, recommended approach.  

The PostScript generated by other Adobe applications (such as PageMaker,
Acrobat, Illustrator, Photoshop, and InDesign) under Windows and MacOS 
have similar characteristics to that created strictly by the OS drivers. 
Although PageMaker generates its own PostScript, that generation is
table-generated based upon the contents of the PPD file, yielding
device-dependent PostScript. In the case of Acrobat, Illustrator,
Photoshop, and InDesign, the application queries the PPD and/or driver
for information about the printer and generates PostScript on that basis.
For these same applications, device controls (bin and paper selection,
duplexing, collating, stapling, spindling, folding) in the form of 
PostScript "setpagedevice" commands are actually inserted by the driver
based on the PPD, not the application. Thus, to summarize, with 
Illustrator, Photoshop, and InDesign, you are best off to directly 
export PDF (PDF is directly generated without an intermediate
generation of PostScript and distillation of same) OR if that isn't
your cup of tea, use the "Acrobat Distiller" / "Create Adobe PDF"
printer instance to generate PostScript and automatically distill.
In the case of PageMaker 7, you can use the "Export Adobe PDF" function
which is implemented as a call to those printer instances in a manner
similar to how "the next major version of FrameMaker" will "save as PDF."

        - Dov



At 3/21/2002 03:06 PM, Thomas Michanek wrote:
>> > When you use FM on UNIX, there you will have simple, deviceindependent
>> > PS-ouput which you can use to produce your PDF-files. No trouble with all
>> > this different drivers....
>> 
>> Unfortunately, what you consider a "feature" others might
>> consider a severe liability. The "device independent" PostScript
>> you refer to is Level 1 PostScript, optimized for nothing and
>> unable to take advantage of features of particular PostScript
>> devices when the PostScript is destined for a real printing
>> device as opposed to the Distiller. 
>
>If we confine the discussion to creating PostScript for use
>with the Distiller to create PDF files, are there any serious
>disadvantages or problems with the generic PostScript created
>by FM on UNIX? Do you miss out on any Acrobat features?
>
>I've created lots of PDFs from FM on UNIX and have never
>encountered any problems at all, regardless if you use Save As
>PDF or Print to PDF (which I think are identically implemented
>on UNIX). This is in stark contrast to all the problems reported
>by Windows users of FM. Personally, I think the generic PostScript
>created by FM on UNIX solves more problems than it creates, and
>I wish there was a similar implementation in Windows.
>
>A related question: Those Adobe applications that in Windows generate
>their own PostScript (without using the Windows GDI?), such as
>PageMaker, how well suited or unsuited is their PostScript for
>subsequent Distilling to PDF? Do the same problems, if any, show
>up as you claim for FM on UNIX?
>
>
>- - - - - - - - - - - - - - - - - - - - - - -
>Thomas Michanek, FrameMaker/UNIX/MIF expert
>Technical Writer, IAR Systems, Uppsala, Sweden
>mailto:Thomas.Michanek@telia.com
>http://go.to/framers/
>- - - - - - - - - - - - - - - - - - - - - - -


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