From: cym224@gmail.com (Nemo)
Subject: [TUHS] Who used *ROFF?
Date: Fri, 11 May 2018 21:40:54 -0400 [thread overview]
Message-ID: <CAJfiPzzeniiZjj0z9p8Y8e==T6WJ0W1B_8iutj4uZaNVTf+iQQ@mail.gmail.com> (raw)
I have read that one of the first groups in AT&T to use early Unix was
the legal dep't, specifically to use *roff to write patent
applications. Can anyone elaborate on this or supply references?
(This would in great contrast to today, where most applications are
written with certain products despite the USPTO, EPO, and others only
accepting PDF versions.) It would also be interesting to learn how
the writers were taught *roff, what editors were used, and what they
thought. (I recall that the secretaries, as they were then called, in
the math dep't used vi to compose plain TeX documents and xdvi to
proofread them.)
N.
next reply other threads:[~2018-05-12 1:40 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 1:40 Nemo [this message]
2018-05-12 2:00 ` Lyndon Nerenberg
2018-05-12 2:11 ` Dave Horsfall
2018-05-12 2:17 ` Lyndon Nerenberg
2018-05-12 2:54 ` Dave Horsfall
2018-05-12 3:19 ` Dave Horsfall
2018-05-12 3:26 ` Lyndon Nerenberg
2018-05-17 15:28 ` Blake McBride
2018-05-12 4:30 ` Grant Taylor
2018-05-12 6:34 ` Dave Horsfall
2018-05-12 11:01 Noel Chiappa
2018-05-12 11:38 ` Clem cole
2018-05-12 18:56 ` Grant Taylor
2018-05-13 13:52 ` Nemo
2018-05-15 1:21 ` Dave Horsfall
2018-05-15 1:32 ` Lyndon Nerenberg
2018-05-15 2:06 ` Bakul Shah
2018-05-15 2:22 ` Jon Steinhart
2018-05-15 2:27 ` Lyndon Nerenberg
2018-05-15 2:45 ` Larry McVoy
2018-05-15 4:51 ` Dave Horsfall
2018-05-15 10:28 ` Jaap Akkerhuis
2018-05-16 0:43 ` Dave Horsfall
2018-05-15 20:49 ` Bakul Shah
2018-05-13 5:55 Rudi Blom
2018-05-14 12:19 Doug McIlroy
2018-05-14 12:41 ` Dave Horsfall
2018-05-14 13:00 ` Ralph Corderoy
2018-05-14 14:45 ` Clem cole
2018-05-14 15:04 ` Larry McVoy
2018-05-14 15:11 ` Larry McVoy
2018-05-14 15:21 ` Jon Steinhart
2018-05-14 15:46 ` Larry McVoy
2018-05-14 15:57 ` Jon Steinhart
2018-05-14 16:41 ` Nemo Nusquam
2018-05-14 18:13 ` arnold
2018-05-14 18:18 ` Jon Steinhart
2018-05-14 18:25 ` Larry McVoy
2018-05-14 18:33 ` Warner Losh
2018-05-14 15:04 ` Clem cole
2018-05-14 15:33 ` arnold
2018-05-14 21:32 ` Jaap Akkerhuis
2018-05-14 21:35 ` Clem Cole
2018-05-14 16:37 ` Ralph Corderoy
2018-05-14 23:04 ` Dave Horsfall
2018-05-14 23:42 ` Ron Natalie
2018-05-14 14:34 ` Larry McVoy
2018-05-14 14:46 ` Clem cole
2018-05-14 21:02 ` Dave Horsfall
2018-05-15 14:07 ` Nemo
2018-05-15 14:37 ` Dan Cross
2018-05-15 14:55 ` Clem cole
2018-05-15 15:10 ` Dan Cross
2018-05-15 12:20 ` Doug McIlroy
2018-05-14 15:10 ` arnold
2018-05-14 15:58 Noel Chiappa
2018-05-14 16:54 ` Warner Losh
2018-05-14 17:13 Noel Chiappa
2018-05-14 21:31 ` Clem Cole
2018-05-15 12:52 Doug McIlroy
2018-05-15 13:40 ` Clem Cole
2018-05-15 14:23 ` arnold
2018-05-15 15:56 ` Ralph Corderoy
2018-05-15 16:33 ` Clem Cole
2018-05-15 16:53 ` Warner Losh
2018-05-15 16:55 ` arnold
2018-05-15 23:45 ` Dave Horsfall
2018-05-15 23:48 ` Larry McVoy
2018-05-16 11:11 ` Dave Horsfall
2018-05-15 14:18 ` arnold
2018-05-15 23:05 Doug McIlroy
2018-05-15 23:12 ` Noel Hunt
2018-05-25 7:01 ` aksr
2018-05-25 7:40 ` Dave Horsfall
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='CAJfiPzzeniiZjj0z9p8Y8e==T6WJ0W1B_8iutj4uZaNVTf+iQQ@mail.gmail.com' \
--to=cym224@gmail.com \
/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).