nevai@function.mps.ohio-state.edu (Paul Nevai) (04/11/91)
Now that I have ugraded my NeXT cube to system software version 2.0 and to board 68040, I noticed that the "c" flag (copies) in dvips stopped working such as in dvips -c 3 foo.dvi I can still use collated copies such as "dvips -C 3 foo.dvi". Can anyone advise me??? I have the following versions of \TeX\ and dvips: This is CTeX, NeXT Version 3.1a This is dvips, version 5.396 (C) 1986-90 Radical Eye Software Thanks...Paul Paul Nevai nevai@mps.ohio-state.edu (Internet) Department of Mathematics nevai@ohstpy (BITNET) The Ohio State University 1-(614)-292-3317 (Office) P.O. Box 3341 1-(614)-292-5310 (Answering Machine) Columbus, OH 43210-0341, USA 1-(614)-459-5615 (FAX)
mcohen@speech-sun.ntt.JP (USR2-Group) (04/15/91)
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.
charlie@wam.umd.edu (Charles William Fletcher) (04/17/91)
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
ken@csis.dit.csiro.au (Ken Yap) (04/18/91)
In article <170516@nttlab.ntt.JP>: >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. It may not be a dvips bug but a PS interpreter bug. Our Dataproducts 1260 dislikes BoundingBoxes larger than the paper size here (A4). (Yes, apparently the interpreter reads the structuring comments!) and produces double height characters. Using -t a4 fixed it.