The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "ozan yigit" <oz@silentrunning.ca>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Documenter's Workbench versions
Date: Thu, 10 Mar 2022 12:21:05 -0500	[thread overview]
Message-ID: <a51b0d27-c2de-4e27-916e-47f728056db7@www.fastmail.com> (raw)
In-Reply-To: <CAK7dMtD6P+=5XHmcyn5KmCn3ys18CjafUsyBD0PW_VWrzsXzSw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]

This is accurate. I was briefly involved with sqtroff, because it was brought to York U
by one of the founders (david slocombe) to publish York's newsletter. 
see this for coach house press history. possibly the first (outside bell) unix-based publisher.
https://publishing.sfu.ca/2015/12/coach-house-press-early-digital-period/

... oz

On Mon, Mar 7, 2022, at 11:55 AM, Kevin Bowling wrote:
> Interesting. That sounds like a different commercial strain, "SoftQuad
> was started in order to improve automated typesetting at Toronto's
> Coach House Press, and for many years developed an enhanced commercial
> version of the text formatting program troff, developed under license
> from AT&T, called sqtroff. It was sold with a suite of associated
> programs, corresponding to AT&T's Documenter's Workbench, under the
> name SoftQuad Publishing Software (SQPS)."
> 
> On Mon, Mar 7, 2022 at 6:28 AM Jaap Akkerhuis <jaapna@xs4all.nl> wrote:
> >
> >
> >
> > > I see documentation of 1.0 (i.e
> > > https://archive.org/details/sysv-dwb/page/n5/mode/2up)
> > > I see a copy of 2.0 for 3B2 (i.e.
> > > https://archives.loomcom.com/3b2/software/Documenters_Workbench/)
> > >
> > > From there things get a little less clear, it seems like we jump to
> > > 3.2 with SysVR3.2?
> >
> > The jump might be due to the effect that for quite a while outside
> > AT&T it was marketed by SoftQuad (Toronto).  (See also
> > <https://en.wikipedia.org/wiki/SoftQuad_Software>).
> >
> >         jaap
> >
> 

ozan s. yigit
http://nextbit.blogspot.com
*to live fully is to wage constant battle against the mundane.* -- guy tal


[-- Attachment #2: Type: text/html, Size: 2988 bytes --]

  reply	other threads:[~2022-03-10 17:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07  1:02 Kevin Bowling
2022-03-07  2:42 ` Larry McVoy
2022-03-07 13:28 ` Jaap Akkerhuis
2022-03-07 16:55   ` Kevin Bowling
2022-03-10 17:21     ` ozan yigit [this message]
2022-03-07 20:57 ` Kevin Bowling
2022-03-09 22:30   ` Andrew Diller
2022-03-10  0:44     ` Kevin Bowling
2022-03-10  2:17       ` Andrew Diller
2022-03-10  1:10   ` Dan Plassche
2022-03-14  0:17     ` Dan Plassche
2022-03-13  5:24 ` Warren Toomey
2022-03-09  2:06 Douglas McIlroy
2022-03-09  9:41 ` Jaap Akkerhuis

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=a51b0d27-c2de-4e27-916e-47f728056db7@www.fastmail.com \
    --to=oz@silentrunning.ca \
    --cc=tuhs@minnie.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).