The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Mychaela Falconia <falcon@freecalypso.org>
To: tuhs@tuhs.org
Subject: [TUHS] My own version of troff
Date: Sun, 07 Jan 2024 13:59:20 -0800	[thread overview]
Message-ID: <20240107215931.4C9043740235@freecalypso.org> (raw)

Hello fellow lovers of old UNIX,

After almost 20 y of intermittent development (started in the fall of
2004), I just made the first official release of my version of troff:

https://www.freecalypso.org/pub/UNIX/components/troff/qjtroff-r1.tar.Z
https://www.freecalypso.org/pub/UNIX/components/troff/qjtroff-r1.tar.gz

(The .Z is the native format; the .gz is for greater accessibility.)

The README file inside the tarball gives the full story, but basically
it is my own derivative from classic V7 troff (not derived from
ditroff, and certainly not groff) that runs under 4.3BSD and emits
PostScript.  Only PS output is supported, no non-PS targets of ditroff.
I started it in 2004, but I still use it to this day (on a real
MicroVAX running my "organically grown" 4.3BSD variant) to write
various TPS reports and technical manuals etc, for my other projects
that don't have much of anything to do with Ancient UNIX.

For anyone who loves intricacies of troff and/or PostScript, you might
find the source code quite interesting to study. :)

Some Time Soon I am hoping to put out my PostScript reprint of the
first 3 books of the 4.3BSD manual set (namely, URM, USD and PRM books)
made with this troff.  The actual book reformatting job is already done
(for these 3 books, not for the other 3 yet), but I need to write new
colophons to be appended (with pstmerge, a tool from my troff suite)
at the end of each book.  (The colophons I wrote for URM and PRM back
in 2012 are in need of corrections and updates, and I didn't have the
USD book done in 2012.)

I will also be responding to BSW's detailed account of V7 PDF reprint
in the other thread shortly - but I wanted to get this troff release
out first, so I won't be in a position of saying "please look at my
creation" when that creation is not publicly accessible.

M~

         reply	other threads:[~2024-01-07 22:00 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 22:17 [TUHS] Original print of V7 manual? Mychaela Falconia
2024-01-05 23:19 ` [TUHS] " segaloco via TUHS
2024-01-06  0:12   ` Will Senn
2024-01-06  1:26   ` Mychaela Falconia
2024-01-06  5:08     ` segaloco via TUHS
2024-01-06  6:12       ` Mychaela Falconia
2024-01-06 15:06       ` Will Senn
2024-01-06  1:06 ` Al Kossow
2024-01-06  1:45   ` segaloco via TUHS
2024-01-06 14:42     ` amp1ron
2024-01-06  3:02   ` Mychaela Falconia
2024-01-06  3:22     ` G. Branden Robinson
2024-01-06  4:06       ` Jonathan Gray
2024-01-06  4:06       ` Mychaela Falconia
2024-01-06 18:33         ` Clem Cole
2024-01-06 21:04           ` Rich Salz
2024-01-06 21:38             ` Clem Cole
2024-01-10 16:32             ` Michael Parson
2024-02-10 19:43               ` Al Kossow
2024-01-07  2:17           ` Mychaela Falconia
2024-01-07  2:25             ` Al Kossow
2024-01-07  2:54             ` Phil Budne
2024-01-07  3:21               ` Mychaela Falconia
2024-01-07  3:55             ` Clem Cole
2024-01-10 16:53             ` Michael Parson
2024-01-10 17:45               ` Clem Cole
2024-01-07 10:54         ` Brian Walden
2024-01-07 12:12           ` arnold
2024-01-08  0:20           ` Mychaela Falconia
2024-01-07 21:59             ` Mychaela Falconia [this message]
2024-01-08  3:24               ` [TUHS] Re: Original print of V7 manual? / My own version of troff G. Branden Robinson
2024-01-08  5:10                 ` Mychaela Falconia
2024-01-08  7:11                   ` G. Branden Robinson
2024-01-09  9:38                     ` Mychaela Falconia
2024-01-09 16:27                       ` Al Kossow
2024-01-09 17:18                         ` segaloco via TUHS
2024-01-09 18:05                           ` Phil Budne
2024-01-09 18:30                             ` Grant Taylor via TUHS
2024-01-09 20:29                           ` Al Kossow
2024-01-09 20:31                             ` Al Kossow
2024-01-09 22:07                           ` Clem Cole
     [not found]                   ` <CAGcdajdc5GfTOeP_Vw_AC0E6BdnrBLape1+GEd2JGDCg4n31eQ@mail.gmail.com>
2024-01-17 14:08                     ` G. Branden Robinson
2024-01-17 15:32                       ` Brad Spencer
2024-01-17 15:48                         ` Clem Cole
2024-01-17 16:25                           ` Rich Salz
2024-01-18  7:00                     ` Mychaela Falconia
     [not found]                       ` <CAGcdaje=RHbLNZv2Cy=xtuEMaYU7RXMtnom7gYuAMMju2xrHgw@mail.gmail.com>
2024-01-18  8:22                         ` Mychaela Falconia
2024-01-18 13:27                       ` G. Branden Robinson
     [not found]                     ` <ZalHs6DAuvRwXTuS@fluorine>
2024-01-19 16:52                       ` G. Branden Robinson
2024-01-06 14:52       ` [TUHS] Re: Original print of V7 manual? Will Senn
2024-01-06 16:52         ` Al Kossow
2024-01-06 16:54           ` Al Kossow
2024-01-06 18:28         ` G. Branden Robinson

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=20240107215931.4C9043740235@freecalypso.org \
    --to=falcon@freecalypso.org \
    --cc=tuhs@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).