unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Convert the hexadecimal character code to the corresponding Unicode value.
Date: Fri, 01 Oct 2021 12:42:25 +0200	[thread overview]
Message-ID: <87ilyhgh66.fsf@zoho.eu> (raw)
In-Reply-To: CAGP6POKnVCSG0hSZdRwpVLdisvQmJUFJxjYGVQAHQ-5efCKxYg@mail.gmail.com

Hongyi Zhao wrote:

> I noticed some comments on the escape syntax used by Emacs
> from here [1-2]. By default, the `describe-char' command
> will give the code point representation of the character in
> hexadecimal and octal formats, say, #o240, #xa0. So, I want
> to if there is a convenient way to do the conversion between
> the hexadecimal character code representation and the
> corresponding Unicode value.

Leads us to the greatest of all human aspirations:

  https://www.youtube.com/watch?v=xA6DtpRuvSQ

Convert between bases:

#! /bin/zsh
#
# this file:
#   http://user.it.uu.se/~embe8573/conf/.zsh/math
#   https://dataswamp.org/~incal/conf/.zsh/math
#
# [...]

change-base () {
    local from=$1
    local to=$2

    local value=$3

    echo "obase=$to; ibase=$from; $value" | bc
}

# _16 ->
hex2dec () { change-base 16 10 $1 }
hex2oct () { change-base 16  8 $1 }
hex2bin () { change-base 16  2 $1 }

# _10 ->
dec2hex () {
    local dec=$1
    local res
    res=$(change-base    10 16 $dec)
    echo $res:l
}
dec2oct () { change-base 10  8 $1 }
dec2bin () { change-base 10  2 $1 }

# _8 ->
oct2hex () {
    local oct=$1
    local res
    res=$(change-base     8 16 $oct)
    echo $res:l
}
oct2dec () { change-base  8 10 $1 }
oct2bin () { change-base  8  2 $1 }

# _2 ->
bin2hex () {
    local bin=$1
    local res
    res=$(change-base     2 16 $bin)
    echo $res:l
}
bin2dec () { change-base  2 10 $1 }
bin2oct () { change-base  2  8 $1 }

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2021-10-01 10:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01 10:27 Convert the hexadecimal character code to the corresponding Unicode value Hongyi Zhao
2021-10-01 10:42 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-10-01 13:14   ` Hongyi Zhao
2021-10-01 17:55     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-02  1:28       ` Hongyi Zhao
2021-10-03  7:40         ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-03  7:44           ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-01 10:58 ` Eli Zaretskii
2021-10-01 13:00   ` Hongyi Zhao
2021-10-01 13:15     ` Eli Zaretskii
2021-10-02  6:20 ` Eduardo Ochs
2021-10-02  7:41   ` Hongyi Zhao
2021-10-02  7:51     ` Eduardo Ochs
2021-10-02  8:13       ` Hongyi Zhao
2021-10-02 17:39         ` Eduardo Ochs
2021-10-03  4:37           ` Hongyi Zhao
2021-10-03  6:05             ` Eduardo Ochs
2021-10-03  7:25               ` Hongyi Zhao

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=87ilyhgh66.fsf@zoho.eu \
    --to=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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).