From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue, 26 Feb 2008 20:46:52 +0100
From: Martin Neubauer <m.ne@gmx.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] troff -man prints poorly
Message-ID: <20080226194652.GA2267@shodan.homeunix.net>
References: <0497b4634bc7e790a2fd0adf29263215@csplan9.rit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0497b4634bc7e790a2fd0adf29263215@csplan9.rit.edu>
User-Agent: Mutt/1.4.2.3i
Topicbox-Message-UUID: 629d12c6-ead3-11e9-9d60-3106f5b1d025

The problem most likely is the missing font informations. If you just use
``dpost -f'' (or the equivalent aux/download ... mentioned earlier) you
should get just what you want. The reason the page display looks good is
that you have access to the fonts as long as you don't leak the postscript
outside a Plan 9 system.

	Martin

* john@csplan9.rit.edu (john@csplan9.rit.edu) wrote:
> I've been writing a man page and wanted to see how it looks
> when formatted with troff and printed, so I tried:
> troff -man <file> | dpost | lp
> only to find that the printout was extremely ugly. Words seem
> to have run together in some very strange ways; if I had a scanner
> handy I could show what I mean. Anyway, the same thing happens
> when I do:
> troff -man /sys/man/1/cat | dpost | lp
> but not when I do:
> troff -ms /sys/doc/asm.ms | dpost | lp
>
> Am I missing something simple and fundamental, or is troff/dpost
> just broken?
>
>
> John