From: Andrew Diller <dillera@gmail.com>
To: Kevin Bowling <kevin.bowling@kev009.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Documenter's Workbench versions
Date: Wed, 9 Mar 2022 21:17:54 -0500 [thread overview]
Message-ID: <283C2A81-4F64-4644-A836-D359E85492E5@gmail.com> (raw)
In-Reply-To: <CAK7dMtC8zP=uV4nnsaoDCii2XGWW6e7+70CQjh6-28wu00ni8g@mail.gmail.com>
Thanks for the info. I managed to delve into the release notes for this package on IRIX. Seems like IRIX has a really nice tool called strangely enough 'relnotes' which will parse and show the release notes like man pages. Here are some snippets from the DWB:
------------
Software Option Product Documenter's
Workbench
Version 4.1.3
Product Code SC4-DWB-4.1.3
System Software Requirements IRIX 5.3 or later
------------
However they do mention this:
-------------
1.3 Product_Support
Silicon Graphics, Inc., provides a comprehensive product
support maintenance program for its products.
If you are in North America and would like support for your
Silicon Graphics-supported products, contact the Technical
Assistance Center at
1-800-800-4SGI.
If you are outside North America, contact the Silicon
Graphics subsidiary or authorized distributor in your
country.
---------------
But they may not answer :)
-andy
> On Mar 9, 2022, at 7:44 PM, Kevin Bowling <kevin.bowling@kev009.com> wrote:
>
>
> It's basically a marketing name for troff and some macro packages.
> You could try feeding some of these
> https://github.com/n-t-roff/DWB3.3/tree/master/doc through it to see
> how it works, although depending on what 4.x really is it may be a bit
> of a learning experience.
>
> Aside from the man pages and official documentation, a lot of popular
> books were and still are written with it
> https://www.troff.org/pubs.html
>
next prev parent reply other threads:[~2022-03-10 2:20 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
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 [this message]
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=283C2A81-4F64-4644-A836-D359E85492E5@gmail.com \
--to=dillera@gmail.com \
--cc=kevin.bowling@kev009.com \
--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).