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: Sun, 03 Jan 2021 17:20:32 +0200 [thread overview]
Message-ID: <83k0sucain.fsf@gnu.org> (raw)
In-Reply-To: <87eej2320z.fsf@mimuw.edu.pl> (jsbien@mimuw.edu.pl)
> From: jsbien@mimuw.edu.pl (Janusz S. Bień)
> Date: Sun, 03 Jan 2021 08:36:28 +0100
>
> PUA stands for Unicode Private Use Area, cf. e.g.
> https://en.wikipedia.org/wiki/Private_Use_Areas.
>
> I use systematically the PUA characters defined by MUFI,
> cf. e.g. https://en.wikipedia.org/wiki/Medieval_Unicode_Font_Initiative.
>
> Recently I made a quick and dirty solution for my own feature request
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32599
>
> (in a slightly different way than suggested originally).
>
> The files and the documentation are available at
> https://github.com/jsbien/unicode4polish in the Emacs-MUFI directory.
>
> Please consider improving and expanding my solution and making it
> available as e.g. ELPA or non-ELPA package.
Thanks.
I may be missing something, but I couldn't find in your Github
repository the infrastructure that could be used to tell Emacs to
interpret arbitrary ranges of PUA codepoints as characters with
certain properties. Could you please point me to the parts I missed?
next prev parent reply other threads:[~2021-01-03 15:20 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 [this message]
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
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=83k0sucain.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.