From: William Staniewicz <wstan@localhostnl.demon.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] troff to PDF
Date: Tue, 20 Feb 2001 11:14:49 -0500 [thread overview]
Message-ID: <20010220101841.CF8BF199E1@mail.cse.psu.edu> (raw)
Is there a cleaner/more direct way of going from a troff to
PDF document? I have it figured out as the following 2 step
process:
troff -mm file.txt | lp -dstdout > file.ps
then,
gs -s'DEVICE=pdfwrite' -s'OutputFile=file.pdf' -r600 -dBATCH -dQUIET -dNOPAUSE file.ps
-Bill
reply other threads:[~2001-02-20 16:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010220101841.CF8BF199E1@mail.cse.psu.edu \
--to=wstan@localhostnl.demon.nl \
--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).