Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 UW 5/3/83; site uw-beaver Path: utzoo!linus!decvax!tektronix!uw-beaver!laser-lovers From: laser-lovers@uw-beaver (laser-lovers) Newsgroups: fa.laser-lovers Subject: Bug in Imagen dviimp Message-ID: <1878@uw-beaver> Date: Wed, 10-Oct-84 17:10:30 EDT Article-I.D.: uw-beave.1878 Posted: Wed Oct 10 17:10:30 1984 Date-Received: Sat, 13-Oct-84 02:45:32 EDT Sender: daemon@uw-beave Organization: U of Washington Computer Science Lines: 19 From: ihnp4!cbosgd!ulysses!mb2c!uofm-cv!doug@uw-beaver.arpa With regards to Mr. Stoekenius' reply to my bug report, my name is Douglas Orr, not David. Also, why are the calculations done first converting to the resolution of the target device? Don't you lose a lot of precision this way? While we are at it, am I correct in my surmise that catdvi does an absolute positioning before each character? Is there some reason for this? I am currently writing a program that produces a dvi format file as its output (from a macwrite file) and want to make sure that I am not missing something. -Douglas Orr ihnp4!uofm-cv!umich!doug doug@umich (csnet)