unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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, Re: bug#65997: 29.1; ?\N{char_name} reference is wrong
Date: Mon, 18 Sep 2023 14:24:48 +0300	[thread overview]
Message-ID: <8334zbg1vj.fsf@gnu.org> (raw)
In-Reply-To: <87pm2fkdmw.fsf@gmail.com> (message from Robert Pluim on Mon, 18 Sep 2023 11:57:11 +0200)

> From: Robert Pluim <rpluim@gmail.com>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>,  awrhygty@outlook.com,
>   65997@debbugs.gnu.org
> Date: Mon, 18 Sep 2023 11:57:11 +0200
> 
>     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.

I already did that (since I had to do this just the other day ;-).





  reply	other threads:[~2023-09-18 11:24 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
2023-09-18  9:57     ` bug#65997: 29.1; ?\N{char_name} reference is wrong, " Robert Pluim
2023-09-18 11:24       ` Eli Zaretskii [this message]
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

  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=8334zbg1vj.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 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).