Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site mtxinu.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!mhuxn!mhuxj!mhuxr!ulysses!allegra!mit-eddie!genrad!decvax!tektronix!hplabs!intelca!qantel!dual!unisoft!mtxinu!ed
From: ed@mtxinu.UUCP (Ed Gould)
Newsgroups: net.text
Subject: Re: ditroff problem?
Message-ID: <290@mtxinu.UUCP>
Date: Tue, 26-Feb-85 19:34:10 EST
Article-I.D.: mtxinu.290
Posted: Tue Feb 26 19:34:10 1985
Date-Received: Mon, 4-Mar-85 04:38:52 EST
References: <351@uvm-cs.UUCP>
Organization: mt Xinu, Berkeley, CA
Lines: 20

> 
> I don't know if this is a bug in deqn, ditroff, or the DEC LN01 postprocessor
> that we have (courtesy of the Unievrsity of Wisconsin).  The following ditroff
> input produces some bad subscripts.  HOWEVER if one changes from 12 point to
> 10 point (remove .ps 12, .sz 12, .nr pp 12, gsize 12), the problem goes away.
> In the line beginning "Thus, if I=...", the subscripts get closer and closer
> to the variables as we go towards the right (in 12 point version). By the time
> we get to "a sub M", the "M" overlaps the "a".  Any ideas?  Thanks.

The text ran fine on my QMS, using the postprocessor I wrote for QMS.
The only thought I have is that eqn needs to know the resolution of
the output device.  Does it correctly know 300/inch?

There's also a comment in the eqn manual about it being tuned for
Roman, Italic, and Bold.  If your fonts are of significantly different
widths and/or aspect rations, that could be the problem, too.

-- 
Ed Gould		    mt Xinu, 739 Allston Way, Berkeley, CA  94710  USA
{ucbvax,decvax}!mtxinu!ed   +1 415 644 0146