GNU bug report logs - #65997
29.1; ?\N{char_name} reference is wrong

Previous Next

Full log

Message #11 received at 65997 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Robert Pluim <rpluim <at> gmail.com>
Cc: 65997 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca, awrhygty <at> outlook.com
Subject: Re: bug#65997: 29.1; ?\N{char_name} reference is wrong
Date: Fri, 15 Sep 2023 21:31:48 +0300

> Cc: Stefan Monnier <monnier <at> iro.umontreal.ca>, 65997 <at> debbugs.gnu.org
> From: Robert Pluim <rpluim <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.