gil@gatech.edu (Gil Neiger) (01/20/89)
Can NeXT use the output of dvi2ps? How can such a postscript file be printed (on the NeXT printer)? Can it be previewed (yet)? - Gil Neiger
ali@polya.Stanford.EDU (Ali T. Ozer) (01/25/89)
In article <17821@gatech.edu> gil@gatech.edu (Gil Neiger) writes: >Can NeXT use the output of dvi2ps? How can such a postscript file be >printed (on the NeXT printer)? Can it be previewed (yet)? Turns out yes, and with not much difficulty. I just played with it some, and the "letter" command in the /@letter routine was causing some trouble. I commented that out, and, voila, the files printed... You should note that the files I was using were generated by dvi2ps 2.00. The comments in the postscript header indicate "last modified Aug 25/85." To preview the output of dvi2ps, you really need a page-oriented previewer. (My little Yap just doesn't cut it; it's good for more interactive Postscript use.) A page-oriented previewer will probably be included in the 0.9 Demos directory. Ali Ozer, NeXT Developer Support aozer@NeXT.com
stevec@fornax.UUCP (Steve Cumming) (01/26/89)
In article <6308@polya.Stanford.EDU>, ali@polya.Stanford.EDU (Ali T. Ozer) writes: > In article <17821@gatech.edu> gil@gatech.edu (Gil Neiger) writes: > >Can NeXT use the output of dvi2ps? How can such a postscript file be > >printed (on the NeXT printer)? Can it be previewed (yet)? > > Turns out yes, and with not much difficulty. I just played with it some, [deleted] > To preview the output of dvi2ps, you really need > a page-oriented previewer. (My little Yap just doesn't cut it; > it's good for more interactive Postscript use.) A page-oriented > previewer will probably be included in the 0.9 Demos directory. > > Ali Ozer, NeXT Developer Support > aozer@NeXT.com 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. I imagine that a deal could be struck with Berkeley... Just a suggestion... Are you listening, NeXT? -- 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.
mbkennel@phoenix.Princeton.EDU (Matthew B. Kennel) (01/28/89)
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