Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!njin!princeton!phoenix!mbkennel
From: mbkennel@phoenix.Princeton.EDU (Matthew B. Kennel)
Newsgroups: comp.sys.next
Subject: Re: dvi2ps on NeXT
Message-ID: <5869@phoenix.Princeton.EDU>
Date: 28 Jan 89 02:13:31 GMT
References: <17821@gatech.edu> <6308@polya.Stanford.EDU> <857@fornax.UUCP>
Reply-To: mbkennel@phoenix.Princeton.EDU (Matthew B. Kennel)
Distribution: na
Organization: Princeton University, NJ
Lines: 28

In article <857@fornax.UUCP> stevec@fornax.UUCP (Steve Cumming) writes:
>
>I seriously suggest that NeXT consider geting access to
>the VorTeX projects dvitool. It is <the> superior 
>previewer.
>
>Now before anyone jumps on me, let me qualfy that.
>It only works for TeX dvi files. But if TeX is what you
>want to work with, that is the correct way to go. 
>It's redundant to turn TeX .dvi files into horriffic
>postscript with scads of downloaded fonts, and then 
>hope that some poor little screen previewer can deal with
>it. None will be able to.

If postscript is what the printer eats, that's what I want to preview!!
Considering that the Next does it's postscript rasterization in the
central CPU box, it had better be able to handle all the downloaded fonts.
If that's the only way to print, I suspect that NeXT will make it a priority
to get the Postscript to work completely.


>Steve Cumming	stevec@lccr.cs.sfu.ca	{uunet|...}!ubc-cs!fornax!stevec
>School of CS
>SFU		(604) 291-4399	        The International Party
>Vancouver, CDN				shall be the human race.

Matt Kennel
mbkennel@phoenix.princeton.edu