unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Francis Belliveau <f.belliveau@comcast.net>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: ASCII - Why...? -- as promised.
Date: Thu, 14 Jan 2021 17:21:11 -0500	[thread overview]
Message-ID: <E927C2CC-6DAF-4E65-BB72-E8074F02384C@comcast.net> (raw)
In-Reply-To: <6CA23431-CF45-4B06-A560-1CE767153BC1@comcast.net>

All,

It was more work that I had expected, and life got in the way a bit, but I put up a page that has my explanation of ASCII.
It can be found at

> http://flb.adamb.me/software/ascii_explaination.html

I would appreciate comments on what I say there.
However, since that will take us far off topic, they should probably not be sent here, but rather directly to me.

I hope that at least some of you find what I have to say on the subject useful.

Fran


> On Jan 9, 2021, at 12:20, Francis Belliveau <f.belliveau@comcast.net> wrote:
> 
> All,
> 
>>> 
>>> You shouldn't mix the hexadecimal and decimal representation of the
>>> characters.  The ASCII characters 0x01-0x1a (inclusive), i.e. the
>>> characters in the range 1-26 (decimal), are the ctrl- variant of the A-Z
>>> ASCII characters (0x41-0x5a).
>> 
>> Why is the ASCII table designed into this strange layout?
>> 
> 
> My answer is that it is not when viewed in light of a binary design implementation.
> This, and a number of similar questions asked previously, has prompted me to write a more extensive explanation of ASCII.  I will post a short off-topic link back here when I put it on-line.
> 
> Fran
> 
> 
> 




  reply	other threads:[~2021-01-14 22:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-09  6:05 The correspondence of the command-name and its key-sequence Hongyi Zhao
2021-01-09  6:32 ` Drew Adams
2021-01-09  7:16   ` Hongyi Zhao
2021-01-09  8:23     ` Omar Polo
2021-01-09  9:33       ` Hongyi Zhao
2021-01-09 10:00         ` Omar Polo
2021-01-11  8:04           ` Hongyi Zhao
2021-01-11  8:20             ` Omar Polo
2021-01-11  9:51               ` tomas
2021-01-09 17:20         ` Francis Belliveau
2021-01-14 22:21           ` Francis Belliveau [this message]
2021-01-09 21:21     ` Drew Adams
2021-01-09 17:39 ` Kévin Le Gouguec
2021-01-09 18:47   ` Eduardo Ochs
2021-01-09 22:29     ` Kévin Le Gouguec

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E927C2CC-6DAF-4E65-BB72-E8074F02384C@comcast.net \
    --to=f.belliveau@comcast.net \
    --cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).