unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: wyuenho@gmail.com, emacs-devel@gnu.org
Subject: Re: Unicode 13 Emoji ranges composed with wrong font on NS port
Date: Mon, 18 Oct 2021 15:58:43 +0300	[thread overview]
Message-ID: <83pms2ebgc.fsf@gnu.org> (raw)
In-Reply-To: <87r1ci4pbd.fsf@gmail.com> (message from Robert Pluim on Mon, 18 Oct 2021 12:09:26 +0200)

> From: Robert Pluim <rpluim@gmail.com>
> Cc: wyuenho@gmail.com,  emacs-devel@gnu.org
> Date: Mon, 18 Oct 2021 12:09:26 +0200
> 
>     Eli> I guess we should have those special codepoints in some list exposed
>     Eli> to Lisp?
>     >> 
>     >> That would avoid having to update two locations if the list ever
>     >> changes, since we could use the list to do the checking in
>     >> font_range.. Would you prefer 'list of codepoints' or 'list of 1-char
>     >> strings containing codepoints'? The latter has a friendlier
>     >> appearance, but would be slightly less efficient due to the need to
>     >> convert between codepoints and 1-char strings.
> 
>     Eli> I think a list of codepoints is better, since usually that's how this
>     Eli> stuff gets communicated.
> 
> OK. emacs-28 or master? (Iʼd argue this is a bugfix to a new feature in
> emacs-28)

Yes, emacs-28, please.

Thanks.



  reply	other threads:[~2021-10-18 12:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-10  8:27 Unicode 13 Emoji ranges composed with wrong font on NS port Jimmy Yuen Ho Wong
2021-10-10 10:52 ` Eli Zaretskii
2021-10-10 15:49   ` Robert Pluim
2021-10-10 17:47     ` Eli Zaretskii
2021-10-11 21:39     ` Jimmy Yuen Ho Wong
2021-10-12 13:12       ` Robert Pluim
2021-10-12 15:49         ` Eli Zaretskii
2021-10-12 17:13         ` Robert Pluim
2021-10-12 18:27           ` Eli Zaretskii
2021-10-13  9:35             ` Robert Pluim
2021-10-13 12:58               ` Eli Zaretskii
2021-10-13 14:59                 ` Robert Pluim
2021-10-13 15:56                   ` Eli Zaretskii
2021-10-14 10:28                     ` Robert Pluim
2021-10-14 11:32                       ` Eli Zaretskii
2021-10-12 17:28         ` Jimmy Yuen Ho Wong
2021-10-12 18:45           ` Eli Zaretskii
2021-10-12 21:00         ` Alan Third
2021-10-13  9:39           ` Robert Pluim
2021-10-12 13:30       ` Eli Zaretskii
     [not found]         ` <88e5c8b0-210d-ef16-8049-6b4d7976b14a@gmail.com>
2021-10-12 18:53           ` Eli Zaretskii
2021-10-13 10:22             ` Robert Pluim
2021-10-13 13:12               ` Eli Zaretskii
2021-10-13 14:52                 ` Robert Pluim
2021-10-13 15:54                   ` Eli Zaretskii
2021-10-14 10:27                     ` Robert Pluim
2021-10-14 11:31                       ` Eli Zaretskii
2021-10-18 10:09                         ` Robert Pluim
2021-10-18 12:58                           ` Eli Zaretskii [this message]
2021-10-19 14:09                             ` Robert Pluim

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=83pms2ebgc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rpluim@gmail.com \
    --cc=wyuenho@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).