Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uwm.edu!uwvax!astroatc!vidiot!brown
From: brown@vidiot.UUCP (Vidiot)
Newsgroups: comp.lang.postscript
Subject: Re: including postscript files in troff files
Message-ID: <1634@vidiot.UUCP>
Date: 18 Apr 91 03:41:38 GMT
References: <5353@ns-mx.uiowa.edu> <1595@vidiot.UUCP> <1383@ecicrl.ocunix.on.ca> <1612@vidiot.UUCP> <1407@ecicrl.ocunix.on.ca>
Reply-To: brown@vidiot.UUCP (Vidiot)
Organization: Vidiot's Hangout
Lines: 32

In article <1407@ecicrl.ocunix.on.ca> clewis@ferret.ocunix.on.ca (Chris Lewis) writes:
<
<Game #1 (simplified):
<	- There is no CAT code corresponding to the letter 'M'.  Eg: in
<	  CAT output, 0115 can never occur.
<	- So, you put this in your CAT troff input:
<	    .tm "Mhello there"
<	- And you use troff thusly:
<		(troff -t ... 2>&1) | cat-2-whatever

I can't find my docs on the CAT output.  In any event, there obviously has
to be a letter M, otherwise there would have been many screwed up documents.

I have to assume that you mean the octal code 115 is not used in the CAT
output codes.  This happens to correspond to the letter M.  Therefore, if
that code appears in the CAT output (actually it doesn't), then it means
something special to the post-processor.

Neat little trick.

The PostScript inclusion files that I have have fixed positions in the
PostScript file and they are not meant to be positioned by the troff itself.
It is meant to be positioned with PostScript code.  That way the troff source
doesn't have to worry about where the characters are positioned.  But, there
are obviously many situations where this does have to happen.

Thanks for the info.  I will keep it handy.  Boy, the games people play to
get around problems. :-)
-- 
      harvard\     att!nicmad\          spool.cs.wisc.edu!astroatc!vidiot!brown
Vidiot  ucbvax!uwvax..........!astroatc!vidiot!brown
      rutgers/  decvax!nicmad/ INTERNET:vidiot!brown%astroatc@spool.cs.wisc.edu