Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!ub!uhura.cc.rochester.edu!rochester!pt.cs.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!wjh+
From: wjh+@andrew.cmu.edu (Fred Hansen)
Newsgroups: comp.text
Subject: embedded postscript
Message-ID: <Qc1kJD200VsP4D7VpE@andrew.cmu.edu>
Date: 13 Apr 91 13:19:11 GMT
Organization: Information Technology Center, Carnegie Mellon, Pittsburgh, PA
Lines: 13

In a personal message James Clark <jclark!jjc@uunet.UU.NET> asked

> How does your scheme for including PostScript in troff files cope with
> the possibility that the PostScript might contain `\' characters?

Since I had never tried a backslash, I got the wrong answer.

The right answer is that you are better off to double every backslash in
a \! line input to troff.

(Fortunately, PostScript requires few backslashes.)

Fred Hansen