all messages for Emacs-related lists mirrored at yhetil.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: Sun, 26 May 2019 17:18:21 +0200	[thread overview]
Message-ID: <86pno56y82.fsf@mimuw.edu.pl> (raw)
In-Reply-To: <83lfyt2s25.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 26 May 2019 17:45:06 +0300")

On Sun, May 26 2019 at 17:45 +03, Eli Zaretskii wrote:
>> From: jsbien@mimuw.edu.pl (Janusz S. Bień)
>> Date: Sun, 26 May 2019 10:10:02 +0200
>> 
>> > First, the MUFI data in a more convenient form are available here:
>> >
>> > On Mon, Aug 27 2018 at  9:00 +0200, jsbien@mimuw.edu.pl writes:
>> >
>> > [...]
>> >
>> >> https://bitbucket.org/jsbien/unihistext/src/master/example/
>> 
>> If you prefer a file pattern after UnicodeData.txt, you can find it
>> here:
>> 
>> http://www.kreativekorp.com/charset/PUADATA/PUBLIC/MUFI/
>> 
>> >
>> > Secondly, other users may be interested in other sets of PUA characters,
>> > cf.
>> >
>> > http://andron-typeforum.xobor.de/t10f13-Towards-a-linguistic-corporate-use-area-LINCUA.html
>> > https://en.wikipedia.org/wiki/ConScript_Unicode_Registry
>> 
>> or Under-ConScript Unicode Registry:
>> 
>> http://www.kreativekorp.com/ucsur/
>
> The UnicodeData.txt file is compiled into Emacs,

I know and I'm curious whether it is really needed. Why it cannot be
loaded at the startup? The advantage would be the user can use always
the up-to-date version of UnicodeData.txt (have you noticed that since
7th May we have now Unicode 12.1 because SQUARE ERA NAME REIWA was
added?).

> but the files you mention cannot be compiled into it, because they
> vary, and because different users might want different lists of
> characters to be supported.  So we need to design how this will work.

My naive idea is to "cheat" Emacs by providing it with the extended data
without changing the original logic. Efficiency is less important than
convenience, perhaps you can "advice"  the 'describe-char' function to
look for the data elsewhere.

> In addition, I think PUA codepoints aren't really treated as
> characters in Emacs, so there's a need for some infrastructure
> changes.

I do not propose to support the supplemental PUA planes. For the BMP
this probably boils down to the availability of the property
information. As we have now a pseudo-UnicodeData.txt for the PUA
characters (at least thise I'm interested in) this doesn't seem to me a
big problem).

> Patches welcome.

Unfortunately I'm unable to provide them myself.

Best regards

Janusz

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





  reply	other threads:[~2019-05-26 15: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ń [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86pno56y82.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 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.