From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: Eduardo Ochs <eduardoochs@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Convert the hexadecimal character code to the corresponding Unicode value.
Date: Sun, 3 Oct 2021 15:25:54 +0800 [thread overview]
Message-ID: <CAGP6PO+7pftDkeN3J0U-VBKQNZkt3N-WWYsum0WVocgU4CymnQ@mail.gmail.com> (raw)
In-Reply-To: <CADs++6isJN4LseazOS+EVpz075FBU-A7N5Ms+ZhFO=2ubr7-Tg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
On Sun, Oct 3, 2021 at 2:05 PM Eduardo Ochs <eduardoochs@gmail.com> wrote:
>
> On Sun, 3 Oct 2021 at 01:38, Hongyi Zhao <hongyi.zhao@gmail.com> wrote:
> >
> > Still, only garbage is generated, as shown in the attachment.
>
> Oops, I didn't realize that there was an implicit question in your
> e-mail...
>
> I use `M-x fea' (a.k.a. `find-echars-around') like this: I visit
> /usr/share/unicode/UnicodeData.txt and I search for characters in it
> by name... for example, suppose that I've found this line in
> UnicodeData.txt:
>
> 2203;THERE EXISTS;Sm;0;ON;;;;;Y;;;;;
$ cat ~/aaa
2203;THERE EXISTS;Sm;0;ON;;;;;Y;;;;;
`C-x C-f ~/aaa RET M-x fea RET'
See the attachment.
>
> it looks interesting, and I know that usually a character that I find
> interesting is part of a family of characters that I will also find
> interesting. So I type M-x fea with point on that line that starts
> with 2203, and it displays the 200 characters before 0x2203, then char
> 0x2203 on a line by itself, then the 200 characters after 0x2203...
>
> I told you that this was just a quick hack, and I though that you
> would look at the code, find references to some functions that you
> were looking for, and use those functions on your code...
Maybe I have not yet understood the level of your use, at least for now.
HZ
[-- Attachment #2: eev-3.png --]
[-- Type: image/png, Size: 118092 bytes --]
prev parent reply other threads:[~2021-10-03 7:25 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
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 [this message]
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=CAGP6PO+7pftDkeN3J0U-VBKQNZkt3N-WWYsum0WVocgU4CymnQ@mail.gmail.com \
--to=hongyi.zhao@gmail.com \
--cc=eduardoochs@gmail.com \
--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).