Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: Computer Old Farts Followers <coff@tuhs.org>
Subject: Re: [COFF] Scribe (Typesetting System) and Unix
Date: Thu, 13 Jan 2022 10:35:46 -0500	[thread overview]
Message-ID: <CAEoi9W7BLg010zGMKmcVhj8-7Qcmp4Ph+-tmz2HUDW6ENRrQGQ@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2NaKgiy3_sD_QziKk1tmAhL+FuHbeTUARkrVEstkKz4aA@mail.gmail.com>


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

On Thu, Jan 13, 2022 at 9:57 AM Clem Cole <clemc@ccc.com> wrote:

> On Wed, Jan 12, 2022 at 10:31 PM Win Treese <treese@acm.org> wrote:
>
>> [snip]
>
> The software was commercially available on UNIX and other systems for
>> some time from a company called Unilogic, later Scribe Systems,
>
> There is a long (and somewhat nasty history history here).  Mike Shamus
> was a one-time CMU CS prof.   He created Unilogic and arranged for the IP
> to be transferred to him.   They had a transpiler that converted
> 'compatible BLISS' (*a.k.a*. Vax Bliss) to other languages.  I believe
> that a flavor of Pascal, Ada and C were possible outputs.   I'm not sure of
> the provenance of the transpiler.   Contemporary with Scribe was the PQCC
> project - Product Quality Compiler Compiler, that Wulf and his students
> were working.  That work forked Tartan labs around the same time as
> Unilogic and I know transpilers had been part of the original work, but I
> never closed the loop.  To be honest they had to have been related in
> some manner, but that all happened after I had left.
>
> At that point, Scribe had been converted from the original PDP-10 version
> to compatible BLISS on VAX/VMS.   Unilogic sold versions of Scribe for
> TOPS, Vax both VMS and Unix, Sun, Apollo and I believe a number of other
> systems (maybe HP and AIX).  The sad part is that history seems to have
> lost both Scribe and the associated transpiler (if anyone knows otherwise,
> I'd love to hear something).
>

I understand that Stallman was deeply affected by both the closed nature of
and "time bombs" in Scribe.


> [snip]
>
> To give ex-CMU and UCB grad, Ken Keller credit. He tried to bridge that
> with his FrameMaker program (which I think Adobe still owns - I have not
> seen much about it in few years and have lost track of Keller).  IIRC Ken's
> program could take a Scribe/LaTex style sheets also.  But FrameMaker (like
> Scribe) was expensive and originally required a UNIX box with 32-bit linear
> addressing to compile, so it was fairly late to the PC.  I never really
> learned it although  Ken gave me a copy early on to play with.  IIRC our
> doc folks at Stellar used it (whereas the Masscomp/ORA folks of the time
> were strictly roff as previously discussed).
>

Does anyone have any experience with Interleaf? That was another in the
lineage of document processors that seems to have fallen into history.

But one could argue that Scribe sort of exists in a way, in LaTeX. My
>> understanding is that Leslie Lamport started LaTex as exactly a way
>> to bring Scribe’s ideas to producing TeX documents, and the basic
>> LaTeX structure looks a lot like Scribe.
>>
> Indeed - that is what I have been told.  I am under the impression that
> early on when Brian started as a Stanford Prof, he had difficulty getting a
> use license from Unilogic even though he was the original author.
> That churn supposedly somehow influenced Leslie WRT to the creation of
> LaTex to make Tex more accessible.
>

Texinfo was supposedly developed as an alternative to Scribe specifically;
I know Arnold has said he really likes it for writing books. I wonder what
the connection between texinfo and latex is, if any at all.

To bring it back to Unix, troff et al are obvious examples of the Unix
philosophy applied to document preparation, while TeX and its progeny have
always felt very foreign to me. They work, of course, but in a way that
feels discordant with respect to the aesthetic of the system. Of course,
TeX originated on the SAIL system, so that makes sense: the PDP-10 world
had different sensibilities than the Unix world. One wonders whether, if
Knuth had been working on a Unix machine instead of SAIL, whether TeX would
have been as chatty as it is; I suspect not.

        - Dan C.

[-- Attachment #1.2: Type: text/html, Size: 5883 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

  parent reply	other threads:[~2022-01-13 15:36 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
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 [this message]
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=CAEoi9W7BLg010zGMKmcVhj8-7Qcmp4Ph+-tmz2HUDW6ENRrQGQ@mail.gmail.com \
    --to=crossd@gmail.com \
    --cc=clemc@ccc.com \
    --cc=coff@tuhs.org \
    /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).