9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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
Date: Tue, 26 Feb 2008 20:46:52 +0100	[thread overview]
Message-ID: <20080226194652.GA2267@shodan.homeunix.net> (raw)
In-Reply-To: <0497b4634bc7e790a2fd0adf29263215@csplan9.rit.edu>

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


  parent reply	other threads:[~2008-02-26 19:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 18:22 john
2008-02-26 18:29 ` Gorka Guardiola
2008-02-26 18:40   ` john
2008-02-27 15:54     ` Russ Cox
2008-02-27 17:25       ` Gorka Guardiola
2008-02-26 18:32 ` Sape Mullender
2008-02-26 18:36   ` john
2008-02-26 19:17     ` Sape Mullender
2008-02-26 19:46 ` Martin Neubauer [this message]
2008-02-26 20:19   ` Sape Mullender

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080226194652.GA2267@shodan.homeunix.net \
    --to=m.ne@gmx.net \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).