From: jsbien@mimuw.edu.pl (Janusz S. Bień)
To: 32599@debbugs.gnu.org
Subject: bug#32599: 25.2; Feature request: input PUA characters by name
Date: Fri, 31 Aug 2018 11:09:59 +0200 [thread overview]
Message-ID: <868t4m3nrs.fsf@mimuw.edu.pl> (raw)
In-Reply-To: <877ek72c7b.fsf@gmail.com> (Robert Pluim's message of "Fri, 31 Aug 2018 10:05:12 +0200")
On Fri, Aug 31 2018 at 10:05 +0200, rpluim@gmail.com writes:
> jsbien@mimuw.edu.pl (Janusz S. Bień) writes:
>
>> On Mon, Aug 27 2018 at 9:00 +0200, jsbien@mimuw.edu.pl writes:
>>> Please extend 'insert-char' to allow using the PUA character names and
>>> codes provided in the format of Unicode named sequences
>>>
>>> http://www.unicode.org/reports/tr34/tr34-23.html
>>>
>>> but containing only single characters.
>
> Iʼm not sure I understand the request: insert-char already supports
> using character names or code points to specify the character. What's
> missing?
You are missing "PUA" in the topic and in the text of my feature
request. PUA is Private Use Area. Cf. e.g.
https://folk.uib.no/hnooh/mufi/
and try to insert a character using such name as 'COMBINING ABBREVIATION
MARK SUPERSCRIPT UR ROUND R FORM'. Cf. also
https://www.unicode.org/mail-arch/unicode-ml/y2018-m08/0096.html
Best regards
Janusz
--
,
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien
next prev parent reply other threads:[~2018-08-31 9:09 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86sh30fg4q.fsf@mimuw.edu.pl>
2018-08-31 6:05 ` bug#32599: 25.2; Feature request: input PUA characters by name Janusz S. Bień
2018-08-31 8:05 ` Robert Pluim
2018-08-31 9:09 ` Janusz S. Bień [this message]
2018-08-31 12:34 ` Robert Pluim
2018-08-31 12:54 ` Janusz S. Bień
2019-05-26 8:10 ` Janusz S. Bień
2019-05-26 14:45 ` Eli Zaretskii
2019-05-26 15:18 ` Janusz S. Bień
2019-05-26 15:48 ` Janusz S. Bień
2019-05-26 16:51 ` Eli Zaretskii
2019-05-26 16:56 ` Eli Zaretskii
2019-05-26 17:33 ` Janusz S. Bień
2019-05-26 18:52 ` Eli Zaretskii
2019-05-27 5:48 ` Janusz S. Bień
2019-05-27 17:11 ` Eli Zaretskii
2019-05-27 17:39 ` Janusz S. Bień
2019-05-27 18:45 ` Eli Zaretskii
2019-05-28 5:18 ` Janusz S. Bień
2019-05-28 5:34 ` Eli Zaretskii
2019-05-28 5:39 ` Janusz S. Bień
2020-12-30 17:49 ` Janusz S. Bień
2020-12-30 20:52 ` Eli Zaretskii
2020-12-31 6:39 ` Janusz S. Bień
2020-12-31 7:49 ` Eli Zaretskii
2020-12-31 8:14 ` Janusz S. Bień
2020-12-31 9:06 ` Eli Zaretskii
2020-12-31 9:31 ` Janusz S. Bień
2020-12-31 10:31 ` Eli Zaretskii
2022-04-26 13:09 ` Lars Ingebrigtsen
2022-04-26 13:30 ` Janusz S. Bień
2022-04-26 13:37 ` Lars Ingebrigtsen
2022-04-26 13:44 ` Janusz S. Bień
2022-04-26 13:45 ` Lars Ingebrigtsen
2022-04-26 15:33 ` Janusz S. Bień
2022-04-26 15:49 ` Robert Pluim
2022-04-26 16:09 ` Janusz S. Bień
2022-04-26 16:44 ` Eli Zaretskii
2022-04-26 18:22 ` Janusz S. Bień
2022-04-27 11:51 ` Lars Ingebrigtsen
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=868t4m3nrs.fsf@mimuw.edu.pl \
--to=jsbien@mimuw.edu.pl \
--cc=32599@debbugs.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).