Article View: comp.text
Article #2501Re: ditroff bug?
From: nils-peter.nelson
Date: Tue, 05 Feb 1991 17:37
Date: Tue, 05 Feb 1991 17:37
14 lines
1191 bytes
1191 bytes
The question was related to a "maladjusted" word. I've never seen such a thing with DWB 3.1. But the most common ditroff problem I see is a failure to tell troff the intended device type. In lieu of any options, DWB 2.0 assumes the APS-5, DWB 3.1 assumes PostScript. The ditroff output is indeed device independent, but justification is based on the character widths associated with the device type. The result is unesthetic interletter spacing, right justification gaffes, etc. My guess is you are using the default spacing (APS?) then running through a postprocessor you got from somewhere that tries to compensate for the differences. Unsuccessfully, apparently.
Technical Details
Message-ID:
<1991Feb5.173726.5396@cbnewsl.att.com>Path:
arc1-ca.pugleaf.net!utzoo!censor!geac!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!rutgers!att!cbnewsl!npnReferences:
<1350@vidiot.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!censor!geac!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!rutgers!att!cbnewsl!npn From: npn@cbnewsl.att.com (nils-peter.nelson) Newsgroups: comp.text Subject: Re: ditroff bug? Summary: troff must know typesetter/printer attributes Message-ID: <1991Feb5.173726.5396@cbnewsl.att.com> Date: 5 Feb 91 17:37:26 GMT Article-I.D.: cbnewsl.1991Feb5.173726.5396 References: <1350@vidiot.UUCP> Organization: AT&T Bell Laboratories Lines: 14