The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] Command-line options
Date: Sun, 27 Mar 2016 13:01:12 +1100	[thread overview]
Message-ID: <20160327020112.GQ3766@eureka.lemis.com> (raw)
In-Reply-To: <alpine.BSF.2.11.1603271221370.15730@aneurin.horsfall.org>

On Sunday, 27 March 2016 at 12:25:05 +1100, Dave Horsfall wrote:
> On Sat, 26 Mar 2016, Ronald Natalie wrote:
>
>> The other fun character set was the old UNIVAC Fielddata.  There were no
>> non printing characters and in fact not even a null value (the 0 value
>> was called master space and printed as @).
>
> What was the character set used by CDC?  60-bit words, of 10 6-bit
> "characters", as I recall...  I thought it was Fielddata, but you're
> saying that that's Univac's.

All octal from here on.

CDC had several different character sets, most called BCD.  They were
unlike Fieldata, which in fact bore some resemblance to ASCII (letters
starting @ABC.. from 0 (or 40 in ASCII), digits starting at 60, ...)

In 7600 BCD, ABC started at 21 (internal) or 61 (external), and digits
started at 00, though in the external form 0 was out of line at 12.
The 3200 system had different coding again; digits were XS3 starting
at about 53.

As if that wasn't enough, the code table I'm looking at right now
(7600) has something called ASCII SUBSET with (upper case) letters
starting at 41 and digits starting at 20.  No idea why they called it
ASCII.

Isn't it wonderful that we no longer have issues with character
representation?

Greg
--
Sent from my desktop computer.
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160327/24df03cd/attachment.sig>


  parent reply	other threads:[~2016-03-27  2:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-25 14:43 [TUHS] Is the Teletype the unsung hero of Unix? Aharon Robbins
2016-03-25 19:47 ` Jaap Akkerhuis
2016-03-25 21:03 ` Diomidis Spinellis
2016-03-28 20:12   ` scj
2016-04-01 14:06     ` Dave Horsfall
2016-04-01 22:41       ` Greg 'groggy' Lehey
2016-03-25 21:29 ` [TUHS] Command-line options Warren Toomey
2016-03-25 23:25   ` Greg 'groggy' Lehey
2016-03-26  2:10     ` John Cowan
2016-03-26  3:09       ` Charles Anthony
2016-03-26 19:43         ` Clem Cole
2016-03-26 20:54           ` Ronald Natalie
2016-03-26 22:05             ` John Cowan
2016-03-27  1:25             ` Dave Horsfall
2016-03-27  1:50               ` Charles Anthony
2016-03-27  2:01               ` Greg 'groggy' Lehey [this message]
2016-03-27  6:18                 ` Random832
2016-03-27  6:57                   ` Greg 'groggy' Lehey
2016-03-27 19:38                   ` Dave Horsfall
2016-03-27  1:35             ` Greg 'groggy' Lehey
2016-03-26  3:54 ` [TUHS] Is the Teletype the unsung hero of Unix? Greg 'groggy' Lehey
2016-03-26  4:30   ` Steve Nickolas
2016-03-26  5:44     ` Greg 'groggy' Lehey
2016-03-26  8:33       ` Steve Nickolas

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=20160327020112.GQ3766@eureka.lemis.com \
    --to=grog@lemis.com \
    /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).