Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: "John P. Linderman" <jpl.jpl@gmail.com>
Cc: Computer Old Farts Followers <coff@tuhs.org>
Subject: Re: [COFF] Scribe (Typesetting System) and Unix
Date: Thu, 13 Jan 2022 11:06:11 -0500	[thread overview]
Message-ID: <CAC20D2O1jhEqEgw+LmhOgxEyACtz2j+kkzTE6dhjshacxGeEEw@mail.gmail.com> (raw)
In-Reply-To: <CAC0cEp-ZYZcEU6JbsuP4W_srxycLcLH5GWZxFv4_zf6qsTyVsA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2125 bytes --]

On Thu, Jan 13, 2022 at 10:08 AM John P. Linderman <jpl.jpl@gmail.com>
wrote:

> Many of us who wrote articles for the Bell System Technical Journal would
> disagree. The BSTJ  publishers could transform something that made sense
> when viewed as troff output into unintelligible gibberish. You cannot split
> a UNIX command line into multiple lines just because it "looks better".
> Sometimes format really matters.
>
I think that is true for any scheme -- professionals and editors need to
work together.  That's what Jon was suggesting.  When they don't have
shared vocabulary/goals -  bad things can happen.   FWIW: I can not speak
for him directly as I never had this conversation with him (Win might
have), but from what I knew/know of Brian Ried I think he might agree with
what I'm suggesting.  IMO, *there will always be cases like the one that
you described*.  This is not particular to any document compiler system.
The question is how to bring the two sides together and who has the high
order bit?

My complaint with Word and the like, is that the 'control' is hidden.  It's
$%^& magic -- why is it indenting here?  Hey I did not tell it to make it
go italics ...

Like Jon and Larry, I'm a big roff fan and still use it.  But to give Brian
his due, his style sheets were in ASCII and what was happening on the page
was fairly easy to deduce.  That said, I never used Scribe for anything
large (like a book), which I can say I have done with troff.  In the late
1970s, I did use Scribe for some papers and found it quite easy to use.
Since that time, as a co-author I've also tried the same with LaTex and/or
Word and found both difficult.  When I have the lead and if I can, I'll use
troff -ms with a few extra Masscomp macros (that ORA used to pass on too --
the Steve Talbot extensions for lists in particular).

So from my professional experience, it has been mostly with troff, my use
of Scribe was short lived.

I'm pretty sure tht Keller tried to make creating books easier in
FrameMaker, as that was one of his target users.  But again I only played
with it, never really had to rely on it for anything.

[-- Attachment #1.2: Type: text/html, Size: 3592 bytes --]

[-- Attachment #2: Type: text/plain, Size: 141 bytes --]

_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff

  reply	other threads:[~2022-01-13 16:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13  2:04 josh
2022-01-13  2:03 ` Greg 'groggy' Lehey
2022-01-13  3:24 ` Win Treese
2022-01-13 14:56   ` Clem Cole
2022-01-13 15:08     ` John P. Linderman
2022-01-13 16:06       ` Clem Cole [this message]
2022-01-13 16:24         ` Warner Losh
2022-01-13 16:39         ` Harald Arnesen
2022-01-13 18:00         ` Bakul Shah
2022-01-13 15:35     ` Dan Cross
2022-01-13 16:02       ` Warner Losh
2022-01-13 16:20         ` Clem Cole
2022-01-13 16:32           ` Warner Losh
2022-01-13 16:42           ` Lars Brinkhoff
2022-01-13 16:52             ` Larry McVoy
2022-01-13 16:54               ` Clem Cole
2022-01-13 17:06               ` Clem Cole
2022-01-13 18:16         ` Dan Cross
2022-01-13 20:00           ` Larry McVoy
2022-01-13 20:26           ` Chet Ramey
2022-01-13 16:13       ` Charles H Sauer
2022-01-13 22:53     ` David Arnold
2022-01-14  1:53       ` Adam Thornton
2022-01-13  3:26 ` Theodore Ts'o
2022-01-13 16:25   ` Larry McVoy
2022-01-13 16:33   ` Dan Cross
2022-01-13 22:19     ` David Arnold
2022-01-13 13:54 ` Adam Sampson
2022-01-13 16:37   ` Lars Brinkhoff

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=CAC20D2O1jhEqEgw+LmhOgxEyACtz2j+kkzTE6dhjshacxGeEEw@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=coff@tuhs.org \
    --cc=jpl.jpl@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).