unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: jsbien@mimuw.edu.pl (Janusz S. Bień)
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32599@debbugs.gnu.org
Subject: bug#32599: 25.2; Feature request: input PUA characters by name
Date: Tue, 28 May 2019 07:18:13 +0200	[thread overview]
Message-ID: <86ftozf97u.fsf@mimuw.edu.pl> (raw)
In-Reply-To: <83lfyr20tx.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 27 May 2019 21:45:30 +0300")

On Mon, May 27 2019 at 21:45 +03, Eli Zaretskii wrote:
>> From: jsbien@mimuw.edu.pl (Janusz S. Bień)
>> Cc: 32599@debbugs.gnu.org
>> Date: Mon, 27 May 2019 19:39:50 +0200
>> 
>> > Asking Emacs to maintain compatibility to various ad-hoc registries
>> > outside of Unicode is not really reasonable.
>> 
>> Yes, but it is not what I propose. I just would the user to be able to
>> use his own definition of PUA provided in the form of an additional
>> UnicodeData.txt (not necessarily as a part of Unicode, it can be perhaps
>> a different coding system).
>
> We don't have infrastructure for reliably doing such customizations on
> user level.  Even importing a new version of the Unicode Standard
> currently requires some manual adaptations, although most of the job
> is done by just rebuilding Emacs after downloading a few UCD files.

I'm intrigued by the need of manual adaptation.

However my main point today is different:

Why our posts are not available neither at

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32599

not at

https://groups.google.com/forum/#!msg/gnu.emacs.bug/SK-RO_OG_GQ/BmUzA-23AgAJ

?

This dosn't allow other users to express their opinion on the matter.

-- 
             ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien





  reply	other threads:[~2019-05-28  5:18 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ń [this message]
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=86ftozf97u.fsf@mimuw.edu.pl \
    --to=jsbien@mimuw.edu.pl \
    --cc=32599@debbugs.gnu.org \
    --cc=eliz@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).