From xemacs-m  Thu Jan 16 14:12:25 1997
Received: from nvwls.cc.purdue.edu (root@nvwls.cc.purdue.edu [128.210.7.3])
          by xemacs.org (8.8.4/8.8.4) with ESMTP
	  id OAA29652 for <XEmacs-Beta@XEmacs.org>; Thu, 16 Jan 1997 14:12:21 -0600 (CST)
Received: from nvwls.cc.purdue.edu (nuspl@localhost [127.0.0.1]) by nvwls.cc.purdue.edu (8.7.5/8.7.3) with ESMTP id PAA27605 for <XEmacs-Beta@XEmacs.org>; Thu, 16 Jan 1997 15:05:14 -0500
Message-Id: <199701162005.PAA27605@nvwls.cc.purdue.edu>
To: XEmacs-Beta@XEmacs.org
Reply-to: nuspl@purdue.edu
X-Mailer: MH-E 5.0.2
X-Attribution: jjn
Subject: Re: PostScript output... 
In-reply-to: Your message of "Thu, 16 Jan 1997 11:11:54 PST."
             <199701161911.LAA32555@newman> 
Mime-Version: 1.0 (generated by tm-edit 7.100)
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 16 Jan 1997 15:05:09 -0500
From: Joe Nuspl <nuspl@nvwls.cc.purdue.edu>


>>>>> "bp" == William M Perry <wmperry@aventail.com> writes:

    bp> Hey, why don't we have a 'postscript' device class?  This
    bp> would kick ass for printing.

Yes.  I came to the same conclusion this summer when I was trying to
re-work ps-print to handle glyphs and variable width fonts.

	Joe

