The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Greg A. Woods" <woods@robohack.ca>
To: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: Re: [TUHS] Seeking wisdom from Unix Greybeards
Date: Wed, 10 Feb 2021 10:57:05 -0800	[thread overview]
Message-ID: <m1l9ufi-0036urC@more.local> (raw)
In-Reply-To: <20201126214825.bDDjr%steffen@sdaoden.eu>

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

At Thu, 26 Nov 2020 22:48:25 +0100, Steffen Nurpmeso <steffen@sdaoden.eu> wrote:
Subject: Re: [TUHS] Seeking wisdom from Unix Greybeards
>
> ANSI escape sequences aka ISO 6429 came via ECMA-48 i have
> learned, and that appeared first in 1976 (that via Wikidpedia).

Wikipedia is a bit misleading here.  This is one case where ANSI and
ECMA worked together quite closely (and another example of where ISO
took the result more or less directly, though on a different schedule).

As it happens one can read about it much more directly from the original
sources.

First we can find that FIPS-86 is "in whole" ANSI-X3.64-1979

	https://nvlpubs.nist.gov/nistpubs/Legacy/FIPS/fipspub86-1981.pdf

Thus giving us "free" access to the original ANSI standard in a "new"
digital (PDF) form.  Here's the full copy of ANSI-X3.64-1979 verbatim
(including cover pages):

	https://nvlpubs.nist.gov/nistpubs/Legacy/FIPS/fipspub86.pdf

See in particular "Appendix H" in the latter.

X3.64 also gives a good list of all the people and organisations which
cooperated to create this standard (though interestingly only mentions
ECMA-48 in that last appendix).

There is also corroborating evidence of this cooperation in the preface
("BRIEF HISTORY") to the 2nd Edition of ECMA-48:

	https://www.ecma-international.org/wp-content/uploads/ECMA-48_2nd_edition_august_1979.pdf

Note though that the link the 1st Edition of ECMA-48 here is wrong, so
as yet I've not seen if there's any history given in that 1st edition):

	https://www.ecma-international.org/publications-and-standards/standards/ecma-48/

As an aside, the DEC VT100 terminal was an early (it came out a year
before X3.64) and relatively complete (for a video terminal application)
implementation of X3.64.

BTW, I would in general agree with Steffen that implementing an
application to output anything but X3.64/ECMA-48/ISO-6429 is rather
pointless these days, _unless_ one wants to take advantage of any
particular implementation's additional "private" features, and/or work
around any annoying but inevitable bugs in various implementations.
Also the API provided by, e.g. libcurses, often makes for much easier
programming than direct use of escape sequences, or invention and
maintenance of one's own API.

--
					Greg A. Woods <gwoods@acm.org>

Kelowna, BC     +1 250 762-7675           RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com>     Avoncote Farms <woods@avoncote.ca>

[-- Attachment #2: OpenPGP Digital Signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2021-02-10 18:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25 17:14 Grant Taylor via TUHS
2020-11-25 17:22 ` Ralph Corderoy
     [not found]   ` <20201126145134.GB394251@mit.edu>
2020-11-26 21:48     ` steffen
2021-02-10 18:57       ` Greg A. Woods [this message]
2021-02-10 22:26         ` Clem Cole
2021-02-24 22:20         ` Steffen Nurpmeso
2020-11-26 21:59     ` dave
2020-11-25 17:38 ` Larry McVoy
2020-11-25 18:00 ` Steffen Nurpmeso
2020-11-25 20:03   ` Steffen Nurpmeso
     [not found] ` <CACYmRNAtdJu0ui=CgrEcWH6J3uikCh0=aCLNvk0+V29rypDBAg@mail.gmail.com>
     [not found]   ` <71fdfa2e-1483-4985-3f55-6760b3a84ec0@gmail.com>
     [not found]     ` <20201126182937.GN9589@mcvoy.com>
2020-11-26 23:14       ` erc
2020-11-26 23:23         ` lm
     [not found] <20201126183746.DD93218C087@mercury.lcs.mit.edu>
     [not found] ` <7DBB40AE-259D-494E-8ABF-2FE4D47F4052@iitbombay.org>
2020-11-26 19:02   ` lars
2020-11-26 21:56   ` steffen

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=m1l9ufi-0036urC@more.local \
    --to=woods@robohack.ca \
    --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).