The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jaap Akkerhuis <jaapna@xs4all.nl>
To: Aharon Robbins <arnold@skeeve.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Troff to ps
Date: Mon, 27 Jul 2020 11:19:36 +0200	[thread overview]
Message-ID: <0D7B784A-1F7E-4377-A307-9C457E8A8C1D@xs4all.nl> (raw)
In-Reply-To: <202007270531.06R5V2OB030883@freefriends.org>


>> When was dpost born?
>> 
>> N.
> 
> Eighth Edition, as part of ditroff.  It wouldn't help on 2.11BSD anyway,
> as dpost reads the ascii intermediate form from ditroff, not the C/A/T
> typesetter codes from original troff.

I don't know when it was born.  It came from the Documentors Work
Bench (DWB).  The DWB used various to create the appropriate font
tables using the target postscript interpreter the fonts were used.
As far as I know, dpost and these tools were created by Rich Drechsler.

	jaap


  reply	other threads:[~2020-07-27  9:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-26 14:56 Will Senn
2020-07-26 15:31 ` arnold
2020-07-26 15:35   ` arnold
2020-07-26 16:15     ` Clem Cole
2020-07-26 17:11       ` arnold
2020-07-26 18:03         ` Clem Cole
2021-01-27  5:24           ` Greg A. Woods
2021-01-28  0:19             ` John Gilmore
2021-01-28  1:25               ` Clem Cole
2021-01-28  1:59                 ` Larry McVoy
2021-01-28  3:19                 ` John Gilmore
2021-01-28 12:58                 ` Clem Cole
2020-07-26 19:05   ` Nemo Nusquam
2020-07-26 22:39     ` Noel Hunt
2020-07-27  5:31     ` arnold
2020-07-27  9:19       ` Jaap Akkerhuis [this message]
2020-07-27 11:07         ` Brad Spencer
2020-07-27 15:58   ` Will Senn
2020-07-26 15:33 ` Clem Cole
2020-07-27 15:53   ` Will Senn
2020-07-26 18:09 ` Al Kossow
2020-07-26 23:37 Norman Wilson
2020-07-27 15:08 ` Jaap Akkerhuis
2020-07-28 11:33 Doug McIlroy

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=0D7B784A-1F7E-4377-A307-9C457E8A8C1D@xs4all.nl \
    --to=jaapna@xs4all.nl \
    --cc=arnold@skeeve.com \
    --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).