From: Drew Adams <drew.adams@oracle.com>
To: jsbien@mimuw.edu.pl
Cc: Help GNU Emacs <help-gnu-emacs@gnu.org>
Subject: RE: AproposUnicode (was: Help with unicode diacritics)
Date: Mon, 28 Dec 2020 10:11:06 -0800 (PST) [thread overview]
Message-ID: <5dded0a0-5970-45c8-ae51-8ec6ccdd50a7@default> (raw)
In-Reply-To: <87czytn7t1.fsf@mimuw.edu.pl>
> > Only partly related to this thread, and just FYI.
> > My library `apu.el' (Apropos Unicode) can sometimes
> > help with showing info about Unicode chars.
>
> I've made a quick test and looks like I would like it, but it seems that
> you completely ignore private use characters. For example, U+E8BF
> described by ‘describe-char’ as general-category: Co (Other, Private
> Use) is completely ignored by `describe-chars-in-region'.
Thanks for trying it.
First, I'm no expert on Unicode, by any means.
I use `get-char-code-property' to check for Unicode
chars, checking properties `name' and `old-name':
(or (get-char-code-property character 'name)
(get-char-code-property character 'old-name))
If a char doesn't have either of those properties
then I flag it as not being a Unicode char.
(Perhaps the message shouldn't say it's not a Unicode
char. I'm no expert on the terminology. Perhaps it
should just say that the char has no name.)
Maybe you can suggest a code change to do something
more like what you expect? If so, please do. Thx.
next prev parent reply other threads:[~2020-12-28 18:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 7:07 Help with unicode diacritics Stephen Eglen
2020-12-28 12:33 ` Skip Montanaro
2020-12-28 13:43 ` Stephen Eglen
2020-12-28 14:48 ` Eli Zaretskii
2020-12-28 16:50 ` Drew Adams
2020-12-28 17:45 ` AproposUnicode (was: Help with unicode diacritics) Janusz S. Bień
2020-12-28 18:11 ` Drew Adams [this message]
2020-12-28 18:16 ` AproposUnicode Janusz S. Bień
2020-12-28 18:40 ` AproposUnicode Drew Adams
2020-12-30 9:51 ` Help with unicode diacritics Stephen Eglen
2020-12-30 17:05 ` Janusz S. Bień
2020-12-30 17:50 ` Stephen Eglen
2020-12-30 20:22 ` Eli Zaretskii
2020-12-28 14:34 ` Eli Zaretskii
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=5dded0a0-5970-45c8-ae51-8ec6ccdd50a7@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=jsbien@mimuw.edu.pl \
/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).