From: "Gorka Guardiola" <paurea@gmail.com>
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 19:29:03 +0100 [thread overview]
Message-ID: <599f06db0802261029x2d7751caxc61d2fd6f56da0d5@mail.gmail.com> (raw)
In-Reply-To: <0497b4634bc7e790a2fd0adf29263215@csplan9.rit.edu>
On Tue, Feb 26, 2008 at 7:22 PM, <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?
>
I normally do:
troff -ms bla.ms|lp -dstout| aux/download -H/sys/lib/postscript/font
-mfontmat|lp -H -d printername
and this works for me. What you describe seem to me what happens when
I don't do the download
and add the fonts to the postscript.
I have never used dpost, and I don't know if it substitutes the aux/download...
I don´t know if you were precisely trying to use dpost not to have to use it...
HTH.
--
- curiosity sKilled the cat
next prev parent reply other threads:[~2008-02-26 18:29 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 [this message]
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
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=599f06db0802261029x2d7751caxc61d2fd6f56da0d5@mail.gmail.com \
--to=paurea@gmail.com \
--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).