Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!pa.dec.com!decuac!haven!wam.umd.edu!charlie
From: charlie@wam.umd.edu (Charles William Fletcher)
Newsgroups: comp.sys.next
Subject: Re: problems with dvips in the 68040 CUBE!!!
Keywords: mode dvips
Message-ID: <1991Apr16.192416.12121@wam.umd.edu>
Date: 16 Apr 91 19:24:16 GMT
References: <1991Apr10.233444.13779@zaphod.mps.ohio-state.edu> <170516@nttlab.ntt.JP>
Sender: usenet@wam.umd.edu (USENET Posting)
Organization: University of Maryland at College Park
Lines: 16
Nntp-Posting-Host: cville

In article <170516@nttlab.ntt.JP> mcohen@speech-sun.NTT.JP (USR2-Group) writes:
>Another dvips bug: the -t switch (setting mode, for different paper
>sizes) blows up, at least for "-t a4", printing oversized characters
>in pseudo-random ways.


I have had a similar problem with the "-t legal" mode. (I reported it
here about a month ago--thanks to everyone who gave me a solution,
unfortunately they didn't solve the problem.) I contacted Rokicki,
but he didn't have a way to check into the problem at this time.
I'm not convinced the problem lies entirely with dvips--for example
when I generate a legal size paper with dvips, YAP displays the entire
page (although offset, which I can then correct). But printing the  
page it always gets chopped off. Anyone got any ideas?

Charlie