From: arnold@cc.gatech.edu (Arnold Robbins)
To: rc@hawkwind.utcs.toronto.edu
Subject: printing the plan 9 manuals
Date: Fri, 6 Nov 1992 12:16:54 -0500 [thread overview]
Message-ID: <9211061716.AA12502@penfold.cc.gatech.edu> (raw)
Has anybody successfully printed the plan 9 doc on a printer using QMS's
Ultrascript posctscrpt interpreter. Our central computing organization
has a Kodak high speed duplexing postscript printer that uses this and it
choked on several of the docs. The ``support'' person send me the errors
and that was it. No response as to whether they could take the problem
up with Kodak.
So, before I go asking Rob Pike what kind of printers they use & how
they generated the postscript, I thought I'd ask others what their
experience was. (I know this isn't rc related, but I didn't want to
do a general net broadcast yet.)
Thanks,
Arnold Robbins --- College of Computing | Ping is the screw-
Georgia Tech, Atlanta, GA 30332-0280 | driver of network
Domain: arnold@cc.gatech.edu Phone: +1 404 894 9214 | debugging tools.
UUCP: uunet!cc.gatech.edu!arnold FAX: +1 404 853 9378 | -- me
next reply other threads:[~1992-11-06 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-11-06 17:16 Arnold Robbins [this message]
1992-11-07 4:59 ` noel
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=9211061716.AA12502@penfold.cc.gatech.edu \
--to=arnold@cc.gatech.edu \
--cc=rc@hawkwind.utcs.toronto.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).