🚀 go-pugleaf

In article <3503@calvin.cs.mcgill.ca> jayem@quiche.cs.mcgill.ca (Jean Marc MONTI) writes:
>So far we've been using FrameMaker 1.3 to make figures, storing them in
>postscript files, and using psfig to include them in LaTeX...
>...  FrameMaker 2.0, and we have been unable to use the same
>technique and the figures don't get printed anymore. Would anybody out
>there know why is this ? Does v2.0 generate something that psfig can't
>understand ?? Where do things go wrong ?? Lastly, is there a fix ??

It does seem that Frame changed something about the way they save PostScript
files.

We do a similar thing with FrameMaker and Eroff, and encountered a similar
problem.  I assume that the problem you are having is that the PostScript
file is an 8.5X11 page overlaying the parent document and "whiting" large
portions of the page or printing somewhere off the page.

This seems to occur on "real" PostScipt devices, but not on our UltraScript QMS
printer.  One thing I did as an experiment (which worked) was this:

1. In FrameMaker, pull up the print menu.

2. As usual, check the "print to .ps file" box.

3. Set the page height to .1" instead of the default 11".

You may have to change the position at which psfig places the imported
PostScript "page" onto the real page.

I realize that this isn't much of a solution, but it may provide some insight
in the problem.  I seems that the proper solution (at least for Eroff
applications) would be for FrameMaker to be able to save to EPS, or for the
importing software to be able to crop the incoming page.

I'm just a dumb customer sharing some meager observations.  Does anyone from
Frame or Elan, or perhaps a LaTeXpert, have any further comments or
assistance?

etan