unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: jsbien@mimuw.edu.pl (Janusz S. Bień)
To: emacs-devel@gnu.org
Subject: Re: Inserting by name and describing some PUA characters
Date: Wed, 06 Jan 2021 16:03:21 +0100	[thread overview]
Message-ID: <87eeiy6rba.fsf@mimuw.edu.pl> (raw)
In-Reply-To: <87eej2320z.fsf@mimuw.edu.pl> ("Janusz S. \=\?utf-8\?Q\?Bie\=C5\=84\?\= \=\?utf-8\?Q\?\=22's\?\= message of "Sun, 03 Jan 2021 08:36:28 +0100")

On Sun, Jan 03 2021 at  8:36 +01, Janusz S. Bień wrote:
> Hi!
>
> PUA stands for Unicode Private Use Area, cf. e.g.
> https://en.wikipedia.org/wiki/Private_Use_Areas.
>
> I use systematically the PUA characters defined by MUFI,
> cf. e.g. https://en.wikipedia.org/wiki/Medieval_Unicode_Font_Initiative.
>
> Recently I made a quick and dirty solution for my own feature request
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32599
>
> (in a slightly different way than suggested originally).
>
> The files and the documentation are available at
> https://github.com/jsbien/unicode4polish in the Emacs-MUFI directory.

I just noticed a serious bug. Looks like I misunderstood the meaning of
'define-char-code-property'.

I hoped that the second call to it will just supplement the table with
additional values. However looks like the table is recreated from
scratch and in consequence it contains only the MUFI names provided by
me.

I will appreciate your help.

Best regards

Janusz

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



  parent reply	other threads:[~2021-01-06 15:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-03  7:36 Inserting by name and describing some PUA characters Janusz S. Bień
2021-01-03 15:20 ` Eli Zaretskii
2021-01-03 15:36   ` Janusz S. Bień
2021-01-03 15:44     ` Eli Zaretskii
2021-01-06 15:03 ` Janusz S. Bień [this message]
2021-01-06 15:52   ` Eli Zaretskii
2021-01-06 16:13     ` Janusz S. Bień
2021-01-06 16:51       ` Eli Zaretskii
2021-01-06 16:53         ` Janusz S. Bień
2021-01-07  8:23           ` Janusz S. Bień

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=87eeiy6rba.fsf@mimuw.edu.pl \
    --to=jsbien@mimuw.edu.pl \
    --cc=emacs-devel@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).