From: Anthony Sorace <anothy@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] instructions to use .eps in troff wanted
Date: Thu, 19 Nov 2009 22:23:42 -0500 [thread overview]
Message-ID: <509071940911191923w1bb27f01w45310a7cdf75ea5@mail.gmail.com> (raw)
In-Reply-To: <4B05C3CD.50700@home.se>
For my company, I generate contracts using troff on Plan 9. The
contracts all contain my digital signature - that is, a postscript
image of my signature - like so:
.BP /usr/a/Pictures/sigs/signature.ps .5 "" "" "" l
I generate postscript for these documents like so:
troff -mm -mpictures foo.mm | lp -d stdout | addpsfonts > foo.ps
next prev parent reply other threads:[~2009-11-20 3:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 9:12 Rudolf Sykora
2009-11-19 9:20 ` Richard Miller
2009-11-19 22:16 ` Jonas Amoson
2009-11-20 3:23 ` Anthony Sorace [this message]
2009-11-20 9:37 ` Rudolf Sykora
[not found] ` <a560a5d00911300623p6343c54ag993b080d3821372e@mail.gmail.com>
2009-12-01 9:26 ` Rudolf Sykora
2009-11-23 12:10 ` matt
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=509071940911191923w1bb27f01w45310a7cdf75ea5@mail.gmail.com \
--to=anothy@gmail.com \
--cc=9fans@9fans.net \
/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).