From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] Who used *ROFF?
Date: Mon, 14 May 2018 11:25:37 -0700 [thread overview]
Message-ID: <20180514182537.GI26148@mcvoy.com> (raw)
In-Reply-To: <201805141818.w4EIImT0016471@darkstar.fourwinds.com>
On Mon, May 14, 2018 at 11:18:48AM -0700, Jon Steinhart wrote:
> arnold at skeeve.com writes:
> > Nemo Nusquam <cym224 at gmail.com> wrote:
> >
> > > On 05/14/18 11:21, Jon Steinhart wrote (in part):
> > > > Also, as part of the book project, I have a script that I've written that
> > > > converts the original troff source into OpenOffice XHTML since my publisher
> > > > won't do troff.
> > >
> > > I am curious about PHI. Tannenbaum praises troff in his prefaces (and
> > > says that all his books are written in troff). Not much on the PHI website.
> > >
> > > N.
> >
> > This is getting off-topic. Prentice Hall (Pearson) generally works with
> > Word but they are able to make allowance for other formats. For sure TeX,
> > and they can work with troff if the author wants to provide the "camera
> > ready copy" themselves (see, for example, Brian's book on Go, done with
> > groff).
> >
> > I wrote my PH book in Texinfo and the converted it to DocBook XML; they
> > used a contractor to actually go from there to typesettable copy.
> >
> > Arnold
>
> Well, this issue, at least in my case, isn't troff per-se. It's that editors
> and such want to be able to read test, make comments in the margins, and track
> changes. I would claim that troff, tex, et. al. are great tools for people
> who write stuff and shepherd it to publication which is great for specs and
> technical papers and all that. What's lacking is tools for the involvement
> of third-parties such as editors.
I've successfully used troff to write our commercial contract.
I collaborated with a guy at Fenwick&West, taught him enough troff -ms
that he could make changes. We sourced 6 different contracts from one doc
and the lawyer *loved* that, he really wanted that fuctionality in Word.
next prev parent reply other threads:[~2018-05-14 18:25 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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 14:59 ` [TUHS] PWB - what is the history? Larry McVoy
2018-05-15 15:13 ` Warner Losh
2018-05-15 15:14 ` Dan Cross
2018-05-15 19:48 ` Lyndon Nerenberg
2018-05-15 20:33 ` John P. Linderman
2018-05-15 21:11 ` Clem Cole
2018-05-15 21:41 ` Lyndon Nerenberg
2018-05-15 15:14 ` Jon Forrest
2018-05-15 15:38 ` Clem Cole
2018-05-15 15:10 ` [TUHS] Who used *ROFF? Dan Cross
2018-05-15 12:20 ` Doug McIlroy
2018-05-14 15:10 ` arnold
-- strict thread matches above, loose matches on Subject: below --
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
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-14 17:13 Noel Chiappa
2018-05-14 21:31 ` Clem Cole
2018-05-14 15:58 Noel Chiappa
2018-05-14 16:54 ` Warner Losh
2018-05-13 5:55 Rudi Blom
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-12 1:40 Nemo
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
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=20180514182537.GI26148@mcvoy.com \
--to=lm@mcvoy.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).