From: ches@cheswick.com (William Cheswick)
Subject: [TUHS] PDP-11, Unix, octal?
Date: Tue, 17 Jan 2017 11:53:04 -0500 [thread overview]
Message-ID: <82A10288-02BE-4898-A4A1-E863286785D4@cheswick.com> (raw)
In-Reply-To: <CMM.0.96.0.1484666091.beebe@gamma.math.utah.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
> On 17Jan 2017, at 10:14 AM, Nelson H. F. Beebe <beebe at math.utah.edu> wrote:
>
> the 1970s. The 6400/6600/7600 family were definitely in the octal
> world. Initially, the character set was 6-bit, with one character
> reserved as an escape to mean that the next 6-bit chunk was to be
> included, giving a 12-bit representation that added support for
> lowercase letters
We called it “half-ASCII”, escaping with codes 74B and 76B. As far as I recall, it only worked
on some versions of some of the timesharing systems in some modes. We never had a lower
case print chain at Lehigh, SO ALL OUR OUTPUT WAS IN UPPER CASE.
And don’t get me started on 63- vs 64- character set.
The availability of ASCII on other operating systems was a great improvement in my life.
And certain neurons still remember crap like 22B is R in display code.
ches
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170117/0a2e9aa8/attachment.html>
next prev parent reply other threads:[~2017-01-17 16:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 19:10 [TUHS] Article on 'not meant to understand this' Steve Johnson
2017-01-16 20:15 ` [TUHS] PDP-11, Unix, octal? Warren Toomey
2017-01-16 20:25 ` Lars Brinkhoff
2017-01-16 22:31 ` ron minnich
2017-01-16 20:31 ` Erik E. Fair
2017-01-17 1:09 ` Steve Johnson
2017-01-17 1:33 ` William Pechter
2017-01-17 14:28 ` Joerg Schilling
2017-01-17 15:14 ` Nelson H. F. Beebe
2017-01-17 16:53 ` William Cheswick [this message]
2017-01-17 14:12 ` Joerg Schilling
2017-01-17 15:28 ` ron minnich
2017-01-16 20:45 Noel Chiappa
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=82A10288-02BE-4898-A4A1-E863286785D4@cheswick.com \
--to=ches@cheswick.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).