Subject: Re: bug#65997: 29.1; ?\N{char_name} reference is wrong, Re: bug#65997: 29.1; ?\N{char_name} reference is wrong

From: Robert Pluim <[email-masked]>
Date: Mon, 18 Sep 2023 11:57:11 +0200

tags 65997 fixed
close 65997 29.2
quit

>>>>> On Fri, 15 Sep 2023 21:31:48 +0300, Eli Zaretskii <[email-masked]> said:

    Eli> 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.

    Eli> They are omitted because their names make no sense, and would just
    Eli> confuse users.

OK.

    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.

    Eli> These 4 should probably be included.  They were excluded because they
    Eli> are in the ranges that were once unused.

OK. Iʼll put a comment in admin/notes/unicode on master for the future.

>>>>> On Fri, 15 Sep 2023 14:57:36 -0400, Stefan Monnier <[email-masked]> said:

    >> 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.

    Stefan> Please adjust the patch so it correct the comment as well :-)

Done.

Closing.
Committed as 6bc3800000c

Robert
--