unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: jsbien@mimuw.edu.pl
Cc: 32599@debbugs.gnu.org
Subject: bug#32599: 25.2; Feature request: input PUA characters by name
Date: Thu, 31 Dec 2020 11:06:28 +0200	[thread overview]
Message-ID: <6F226CA9-23AB-4D17-8674-6CD8F9907437@gnu.org> (raw)
In-Reply-To: <87bleamlxq.fsf@mimuw.edu.pl>

On December 31, 2020 10:14:41 AM GMT+02:00, jsbien@mimuw.edu.pl wrote:
> On Thu, Dec 31 2020 at  9:49 +02, Eli Zaretskii wrote:
> > On December 31, 2020 8:39:03 AM GMT+02:00, jsbien@mimuw.edu.pl
> wrote:
> >> So the PUA names are to be added to ucs-names in mule-cmds.el. At
> >> first
> >> glance it doesn't seem difficult, as I already have them in the
> form
> >> of 
> >> uni-name.el. I will work on it after New Year.
> >
> > What would be the advantage of adding names for PUA codepoints?
> 
> To make it clear: I'm not adding names to PUA codepoints, I add to
> Emacs
> the names already in use for some PUA codepoints.
> 
> > The disadvantage is clear: bloating the Emacs process memory
> footprint
> > by some 137,000 strings of some non-descriptive form, like
> > PUA-CHARACTER-nn.
> 
> What do you need PUA-CHARACTER-nn for? I never proposed anything like
> this.
> 
> Moreover:
> 
> There is always price for everything.
> 
> BTW, not 137,000 but 739 for MUFI 4.0 and a little more for the
> current 
> version.

OK, it wasn't clear that you want to add MUFI codepoints.

However, if that is the intent, I think we should first discuss whether we want to add PUA codepoints defined by the different initiatives, and if so, which ones.  MUFI is not the only such collections, there are others.

We could instead wait until these codepoints are incorporated into the Unicode Standard (as already happened with some MUFI codepoints).  Or we might decide that we want to add some infrastructure which could be used by users to add support for ranges of PUA without adding that by default.

IOW, I think this kind of changes should be discussed first, and the place to discuss them is not here, it's on emacs-devel.





  reply	other threads:[~2020-12-31  9:06 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ń
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 [this message]
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=6F226CA9-23AB-4D17-8674-6CD8F9907437@gnu.org \
    --to=eliz@gnu.org \
    --cc=32599@debbugs.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 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).