From: Eli Zaretskii <eliz@gnu.org>
To: Howard Melman <hmelman@gmail.com>
Cc: larsi@gnus.org, 54970@debbugs.gnu.org, rpluim@gmail.com, alan@idiocy.org
Subject: bug#54970: 28.1; Some emoji no longer display
Date: Sun, 17 Apr 2022 21:00:11 +0300 [thread overview]
Message-ID: <838rs3y4ic.fsf@gnu.org> (raw)
In-Reply-To: <A47F8732-4206-49FB-96D8-45EE84685FB9@gmail.com> (message from Howard Melman on Sun, 17 Apr 2022 12:48:32 -0400)
> From: Howard Melman <hmelman@gmail.com>
> Date: Sun, 17 Apr 2022 12:48:32 -0400
> Cc: Robert Pluim <rpluim@gmail.com>,
> Alan Third <alan@idiocy.org>,
> Lars Ingebrigtsen <larsi@gnus.org>,
> 54970@debbugs.gnu.org
>
> > So the example didn't work, because you do have a font for those
> > characters. Can you find some characters that don't have fonts? For
> > example, do any of the scripts in etc/HELLO show as tofu or "blank"?
> >
> > (I'm trying to understand why you had those blank displays where you
> > should have seen tofu; if you are not interested in trying to figure
> > this out further, I'm fully prepared to stop asking questions.)
>
> I'm willing. FYI, I'm using the prebuilt emacs 28 from https://emacsformacosx.com/
> I don't build my own.
>
> Here are two images showing the whole HELLO file.
You have too many fonts ;-) It is strange that with so many fonts the
U+1F37D couldn't be displayed.
Okay, try with codepoints between D800 and DB7F: what does that
produce?
next prev parent reply other threads:[~2022-04-17 18:00 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 13:07 bug#54970: 28.1; Some emoji no longer display Howard Melman
2022-04-16 14:18 ` Lars Ingebrigtsen
2022-04-16 14:55 ` Lars Ingebrigtsen
2022-04-16 15:27 ` Howard Melman
2022-04-16 16:02 ` Alan Third
2022-04-16 16:21 ` Howard Melman
2022-04-16 16:42 ` Eli Zaretskii
2022-04-16 17:17 ` Howard Melman
2022-04-16 18:26 ` Eli Zaretskii
2022-04-16 19:19 ` Howard Melman
2022-04-16 19:22 ` Eli Zaretskii
2022-04-16 20:07 ` Howard Melman
2022-04-17 5:53 ` Eli Zaretskii
2022-04-17 13:34 ` Robert Pluim
2022-04-17 14:35 ` Howard Melman
2022-04-17 15:14 ` Robert Pluim
2022-04-17 18:44 ` Howard Melman
2022-04-17 18:49 ` Lars Ingebrigtsen
2022-04-17 18:56 ` Howard Melman
2022-04-17 18:58 ` Eli Zaretskii
2022-04-17 19:40 ` Howard Melman
2022-04-17 22:03 ` Howard Melman
2022-04-18 5:12 ` Eli Zaretskii
[not found] ` <0AC9BAB0-35AA-4088-BEEB-66D5B0459FC2@gmail.com>
2022-04-18 13:19 ` Howard Melman
2022-04-22 21:56 ` Howard Melman
2022-04-23 7:51 ` Eli Zaretskii
2022-04-23 16:35 ` Howard Melman
2022-04-23 16:58 ` Eli Zaretskii
2022-04-23 17:22 ` Howard Melman
2022-04-23 17:46 ` Eli Zaretskii
2022-04-23 19:12 ` Howard Melman
2022-04-23 9:46 ` Eli Zaretskii
2022-04-17 14:35 ` Howard Melman
2022-04-17 14:44 ` Eli Zaretskii
2022-04-17 14:50 ` Howard Melman
2022-04-17 15:50 ` Eli Zaretskii
2022-04-17 15:54 ` Howard Melman
2022-04-17 16:17 ` Eli Zaretskii
2022-04-17 16:48 ` Howard Melman
2022-04-17 18:00 ` Eli Zaretskii [this message]
2022-04-17 18:09 ` Howard Melman
2022-04-17 18:27 ` Lars Ingebrigtsen
2022-04-17 18:36 ` Eli Zaretskii
2022-04-17 18:45 ` Lars Ingebrigtsen
2022-04-17 18:54 ` Howard Melman
2022-04-17 18:58 ` Eli Zaretskii
2022-04-17 19:27 ` Alan Third
2022-04-17 19:47 ` Alan Third
2022-04-17 20:34 ` Alan Third
2022-04-17 21:05 ` Howard Melman
2022-04-18 4:29 ` Eli Zaretskii
2022-04-18 13:19 ` Alan Third
2022-04-18 14:23 ` Eli Zaretskii
2022-04-18 19:28 ` Alan Third
2022-04-19 1:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-19 3:51 ` Alan Third
2022-04-17 18:34 ` Eli Zaretskii
2022-04-17 18:46 ` Howard Melman
2022-04-17 19:00 ` Eli Zaretskii
2022-04-17 19:47 ` Howard Melman
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=838rs3y4ic.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54970@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=hmelman@gmail.com \
--cc=larsi@gnus.org \
--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).