From: наб <nabijaczleweli@nabijaczleweli.xyz>
To: tech@mandoc.bsd.lv
Subject: Should .At 32v rather be [AT&T] UNIX/32V rather than Version 32 AT&T UNIX?
Date: Wed, 18 Aug 2021 20:46:52 +0200 [thread overview]
Message-ID: <20210818184652.gp3apndkyoa2m3kc@tarta.nabijaczleweli.xyz> (raw)
[-- Attachment #1: Type: text/plain, Size: 1951 bytes --]
Hi!
At present:
-- >8 --
$ printf '.At v7\n\n.At 32v' | ./mandoc -mdoc
UNTITLED LOCAL UNTITLED
Version 7 AT&T UNIX
Version 32V AT&T UNIX
-- >8 --
But I believe it should read:
-- >8 -
$ printf '.At v7\n\n.At 32v' | ./mandoc -mdoc
UNTITLED LOCAL UNTITLED
Version 7 AT&T UNIX
AT&T UNIX/32V
-- >8 --
My reasoning being that 32V is a direct port of V7 to the VAX
with single-digit and non-formative new utilities (tsort, ..?);
bundling it in with V[1234567] is, at its best, disingenuous,
and, at worst, just plainly wrong.
The designations of early unices originate in their manuals;
how does 32V stack up here?
/usr/man/man0/title:
-- >8 --
Bell Telephone Laboratories, Incorporated
Holmdel, New Jersey
UNIX/32V PROGRAMMER’S MANUAL
Version 1.0
February, 1979
-- >8 --
/usr/man/man0/title] (TM in superscript):
-- >8 --
‐‐
UNIXTM/32V TIME‐SHARING SYSTEM:
UNIX PROGRAMMER’S MANUAL
Version 1.0, Volume 1
February, 1979
Bell Telephone Laboratories, Incorporated
Holmdel, New Jersey
-- >8 --
In both cases, the manual is designated as Version 1.0 for "UNIX/32V".
The fundamental .At contract is to include "AT&T UNIX",
hence why I think "AT&T UNIX/32V" is best.
32V is available for autopsy at
http://ftp.okass.net/pub/mirror/minnie.tuhs.org/Distributions/USDL/32V/32v_usr.tar.gz
For the record and paralleling major implementations,
I've raised this as for groff as Debian #991633:
https://bugs.debian.org/991633
The same reasoning is laid out there, no comments at this time.
Looking forward to your thoughts!
Best,
наб
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2021-08-18 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 18:46 наб [this message]
2021-08-19 6:34 ` Guy Harris
2021-08-19 11:54 ` наб
2021-08-19 15:13 ` Ingo Schwarze
2021-09-01 16:53 ` наб
2021-09-02 12:40 ` Ingo Schwarze
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=20210818184652.gp3apndkyoa2m3kc@tarta.nabijaczleweli.xyz \
--to=nabijaczleweli@nabijaczleweli.xyz \
--cc=tech@mandoc.bsd.lv \
/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).