From: Eli Zaretskii <eliz@gnu.org>
To: jsbien@mimuw.edu.pl
Cc: emacs-devel@gnu.org
Subject: Re: Inserting by name and describing some PUA characters
Date: Wed, 06 Jan 2021 18:51:49 +0200 [thread overview]
Message-ID: <83sg7e100q.fsf@gnu.org> (raw)
In-Reply-To: <875z4a59hl.fsf@mimuw.edu.pl> (jsbien@mimuw.edu.pl)
> From: jsbien@mimuw.edu.pl (Janusz S. Bień)
> Cc: emacs-devel@gnu.org
> Date: Wed, 06 Jan 2021 17:13:42 +0100
>
> --8<---------------cut here---------------start------------->8---
>
> (define-char-code-property 'name
> #^[nil nil char-code-property-table nil #^^[1 0 nil nil nil nil nil
>
> [...]
>
> J JJ C K T P H] [A AE YA YAE EO E YEO YE O WA WAE OE YO U WEO WE WI YU EU YI I] [G GG GS N NJ NH D L LG LM LB LS LT LP LH M B BS S SS NG J C K T P H]]]]
> "Unicode character name.
> Property value is a string or nil.
> The value nil stands for the default value \"null string\").")
>
> --8<---------------cut here---------------end--------------->8---
>
> I expected that the names of the PUA MUFI characters will be added to
> the existing Unicode names. However after evaluating it 'describe-char'
> doesn't show the names of the Unicode character. I assume the culprit is
> 'mufi-name.el' but of course the problem can be more complicated.
I think with the current infrastructure you will have to regenerate
uni-name.el such that it includes information both from
UnicodeData.txt and from MUFI. uni-name.el will then be loaded when
first used.
Alternatively, I think you could use put-char-code-property to modify
the 'name' property of the PUA codepoints you want to use for MUFI.
next prev parent reply other threads:[~2021-01-06 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 7:36 Inserting by name and describing some PUA characters Janusz S. Bień
2021-01-03 15:20 ` Eli Zaretskii
2021-01-03 15:36 ` Janusz S. Bień
2021-01-03 15:44 ` Eli Zaretskii
2021-01-06 15:03 ` Janusz S. Bień
2021-01-06 15:52 ` Eli Zaretskii
2021-01-06 16:13 ` Janusz S. Bień
2021-01-06 16:51 ` Eli Zaretskii [this message]
2021-01-06 16:53 ` Janusz S. Bień
2021-01-07 8:23 ` Janusz S. Bień
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83sg7e100q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.