unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Deniz Dogan <deniz.a.m.dogan@gmail.com>
Cc: help-gnu-emacs@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: How switch from escaped octal character code to escaped HEX?
Date: Mon, 3 Jan 2011 15:37:34 +0100	[thread overview]
Message-ID: <5ECF2988-32AC-4558-90BF-4E36DF960966@Web.DE> (raw)
In-Reply-To: <AANLkTinrOvv6D63L9KzXjeVpFvkf94_s2n0xTD4LQ1zd@mail.gmail.com>


Am 03.01.2011 um 11:13 schrieb Deniz Dogan:

> I read on Wikipedia: "Octal representation of non-ASCII bytes may be
> particularly handy with UTF-8, where any start byte has octal value
> \3nn and any continuation byte has octal value \2nn."
>
> Is this the reason perhaps?

Certainly not! GNU Emacs was octal before someone imagined "Unicode"...

It comes from sparse memory. One byte is two nibbles! (1 € is almost 2  
ancient DM.) UNIX file permissions are octal. C is great in shifting  
bits around.

--
Greetings

   Pete

Almost anything is easier to get into than out of.
				– Allen's Law




  reply	other threads:[~2011-01-03 14:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-28 15:39 How switch from escaped octal character code to escaped HEX? Oleksandr Gavenko
2010-12-28 15:51 ` Oleksandr Gavenko
     [not found] ` <mailman.6.1293551515.18545.help-gnu-emacs@gnu.org>
2011-01-03  4:23   ` Stefan Monnier
2011-01-03  7:14     ` Deniz Dogan
2011-01-03 10:13       ` Deniz Dogan
2011-01-03 14:37         ` Peter Dyballa [this message]
2011-01-04  4:03       ` Stefan Monnier
     [not found]     ` <mailman.8.1294038895.27854.help-gnu-emacs@gnu.org>
2011-01-03 13:42       ` Barry Margolin
2011-01-11 10:23     ` Oleksandr Gavenko
     [not found]     ` <mailman.0.1294741438.20926.help-gnu-emacs@gnu.org>
2011-01-11 17:34       ` Stefan Monnier
2011-01-12  9:22         ` Oleksandr Gavenko

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=5ECF2988-32AC-4558-90BF-4E36DF960966@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=deniz.a.m.dogan@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).