🚀 go-pugleaf

In article <1307@m1.cs.man.ac.uk> mario@madarch.man.ac.uk (Mario Wolczko) writes:

..... discussion of difficulty importing FrameMaker 2.0 PS files into LaTeX

   We have encountered exactly the same problem.  In 2.0, the folks who
   wrote it were kind enough to ensure that no matter what you do, the
   PostScript generated by Maker cannot be included in another document,
   because it messes with global things.  It also carefully obliterates
   part of the page before drawing anything.  When I called our support
   number about this, at first I couldn't get them to understand what on
   earth I was talking about ("Why not stop using LaTeX anyway?"), and
   then they said it wouldn't be fixed.  If anyone from Frame is out
   there, *please fix this*.  It's antisocial to produce PostScript that
   cannot be imported.

I think it's a lot worse than antisocial.  It is at least unethical,
maybe outright dishonest.  If the manufacturer is doing this on
purpose than he is deliberately sabotaging his own customers.

My own employers (for whom I do not speak) are currently looking over
Frame and some other DTP packages.  If Frame's makers are deliberately
crippling their product to prevent us from using it as a generic tool
to produce PS files (and I regard unwillingness to correct such a
severe shortcoming as "deliberate"), then I think it will not be too
difficult to ensure that, whatever we end up using, it will not be
FrameMaker.

--

   Martin L. Smith             Amoco Research Center
                               P.O. Box 3385
 zmls04@trc.amoco.com          Tulsa, OK 74102
[zmls04@sc.msc.umn.edu]        918-660-4065