From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 65997@debbugs.gnu.org, monnier@iro.umontreal.ca, awrhygty@outlook.com
Subject: bug#65997: 29.1; ?\N{char_name} reference is wrong
Date: Fri, 15 Sep 2023 21:31:48 +0300 [thread overview]
Message-ID: <83il8bjnjf.fsf@gnu.org> (raw)
In-Reply-To: <87y1h7jvsa.fsf@gmail.com> (message from Robert Pluim on Fri, 15 Sep 2023 17:33:41 +0200)
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 65997@debbugs.gnu.org
> From: Robert Pluim <rpluim@gmail.com>
> Date: Fri, 15 Sep 2023 17:33:41 +0200
>
> For a minute there I thought our hash tables were broken :-). Stefan,
> it only took 9 years, but this is no longer true:
>
> lisp/international/mule-cmds.el:
>
> ;; In theory this code could end up pushing an "old-name" that
> ;; shadows a "new-name" but in practice every time an
> ;; `old-name' conflicts with a `new-name', the newer one has a
> ;; higher code, so it gets pushed later!
>
> The patch below fixes that issue.
Please install on the emacs-29 branch, and thanks.
> awrhygty> output(TANGUT COMPONENTs are omitted):
>
> I donʼt know why the ranges in `ucs-names' donʼt cover these
> code-points. Itʼs easy enough to change them, but theyʼre
> explicitly commented out.
They are omitted because their names make no sense, and would just
confuse users.
> awrhygty> 16FE4 KHITAN SMALL SCRIPT FILLER 0 error
> awrhygty> 16FF0 VIETNAMESE ALTERNATE READING MARK CA 0 error
> awrhygty> 16FF1 VIETNAMESE ALTERNATE READING MARK NHAY 0 error
> awrhygty> 1B132 HIRAGANA LETTER SMALL KO 0 error
>
> And similarly for these 4.
These 4 should probably be included. They were excluded because they
are in the ranges that were once unused.
next prev parent reply other threads:[~2023-09-15 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 13:02 bug#65997: 29.1; ?\N{char_name} reference is wrong awrhygty
2023-09-15 15:33 ` Robert Pluim
2023-09-15 18:31 ` Eli Zaretskii [this message]
2023-09-18 9:57 ` bug#65997: 29.1; ?\N{char_name} reference is wrong, " Robert Pluim
2023-09-18 11:24 ` Eli Zaretskii
2023-09-15 18:57 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83il8bjnjf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65997@debbugs.gnu.org \
--cc=awrhygty@outlook.com \
--cc=monnier@iro.umontreal.ca \
--cc=rpluim@gmail.com \
/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.