The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Ralph Corderoy <ralph@inputplus.co.uk>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Found and Purchased Unix 4.1 3B20S Manual
Date: Mon, 12 Dec 2022 08:25:09 -0600	[thread overview]
Message-ID: <20221212142509.oo7cev6o6yzvh4gs@illithid> (raw)
In-Reply-To: <20221212140548.2648621CFF@orac.inputplus.co.uk>

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

At 2022-12-12T14:05:48+0000, Ralph Corderoy wrote:
> > I am curious about this "osd" macro package.  What was it for?
> 
> From mosd(5) in
> http://www.bitsavers.org/pdf/altos/3068/690-15843-001_Altos_Unix_System_V_Documenters_Workbench_Vol_1_Jul85.pdf
> 
>     NAME 
>         mosd - the OSDD adapter macro package for formatting documents
> 
>     DESCRIPTION 
>         The OSDD adapter macro package is a tool used in conjunction with
>         the MM macro package to prepare Operations Systems Deliverable
>         Documentation.  Many of the OSOD Standards are different from
>         the default format provided by MM.  The OSOD adapter package
>         sets the appropriate MM options for automatic production of the
>         OSDO Standards.  The OSOO adapter package also generates the
>         correct OSDD page headers and footers, heading styles, Table of
>         Contents format, etc.

Thanks, Ralph!

Regards,
Branden

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2022-12-12 14:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02  5:04 [TUHS] " segaloco via TUHS
2022-12-02  9:36 ` [TUHS] " Sergio Pedraja
2022-12-11  0:07 ` Jason T
2022-12-11  2:21   ` segaloco via TUHS
2022-12-11  6:28     ` John Cowan
2022-12-12  6:15       ` segaloco via TUHS
2022-12-12 13:38         ` G. Branden Robinson
2022-12-12 14:05           ` Ralph Corderoy
2022-12-12 14:25             ` G. Branden Robinson [this message]

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=20221212142509.oo7cev6o6yzvh4gs@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=ralph@inputplus.co.uk \
    --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).