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: Mon, 27 May 2019 20:11:51 +0300	[thread overview]
Message-ID: <83r28j2560.fsf@gnu.org> (raw)
In-Reply-To: <86woic4fd5.fsf@mimuw.edu.pl> (jsbien@mimuw.edu.pl)

> From: jsbien@mimuw.edu.pl (Janusz S. Bień)
> Cc: 32599@debbugs.gnu.org
> Date: Mon, 27 May 2019 07:48:38 +0200
> 
> On Sun, May 26 2019 at 21:52 +03, Eli Zaretskii wrote:
> 
> [...]
> 
> > Personally, I'm surprised people use PUA for
> > these purposes,
> 
> Which purposes?

The purposes of mainstream text editing.  Are there other comparable
applications that let users define fonts for PUA codepoints, define
their attributes, and then manipulate those characters as any other?

> > and even more surprised they expect Emacs to support
> > this.  But that's me.
> 
> PUA characters, especially MUFI, are needed to typeset some
> texts. (XeLa)TeX is still a very good typesetting system and Emacs-based
> AUCTeX is still a very good tool to use TeX.

Those are separate projects.  If they need to use non-standard
characters with corresponding non-standard fonts, they could maintain
some add-on packages for Emacs to do that.

Asking Emacs to maintain compatibility to various ad-hoc registries
outside of Unicode is not really reasonable.  How will we know which
PUA codepoints to support?  How would we know which registered
codepoints are stable enough and wide-spread enough to justify their
support in Emacs?  How will we keep track of the changes in these
areas?  This is a task for someone who is an expert in this domain, is
aware of all the important developments there, and who can update
Emacs whenever something important changes.  As things are, we have
trouble even tracking the Unicode Standard: each new edition takes
several hours to incorporate, run the tests, make the necessary
changes, etc.

I guess what I'm saying is that without a dedicated volunteer who
would take care of this issue we can only wish such support will be
added, but we have no real hope it will materialize, except by some
enormous luck.

Of course, if you know someone who could be persuaded to come on board
and work on this now and in the future, I think the feature will be
welcome.

Thanks.





  reply	other threads:[~2019-05-27 17:11 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 [this message]
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=83r28j2560.fsf@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).