unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 44020@debbugs.gnu.org, alan@idiocy.org, rpluim@gmail.com
Subject: bug#44020: 28.0.50; Prefer selection of colour emoji fonts?
Date: Sun, 18 Oct 2020 10:09:09 +0200	[thread overview]
Message-ID: <87lfg4klay.fsf@gnus.org> (raw)
In-Reply-To: <83k0vptdvq.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 17 Oct 2020 12:12:25 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> On the third hand, since it's preinstalled, Emacs doesn't need to
>> mention it, because it's always there, and Emacs won't have problems
>> displaying the characters it offers.
>
> Are you sure?  What exactly makes sure Emacs won't have any problems
> in those cases?  For starters, does Emacs really know that a given
> character belongs to "Emoji"?  And if it does, does it know how to
> filter fonts that support Emoji?

I thought that Emacs looped through all the fonts on the system and
checked whether the font had coverage for the character we wanted to
display?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-10-18  8:09 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15 18:10 bug#44020: 28.0.50; Prefer selection of colour emoji fonts? Lars Ingebrigtsen
2020-10-15 18:52 ` Eli Zaretskii
2020-10-16  8:19   ` Robert Pluim
2020-10-16 10:26     ` Eli Zaretskii
2020-10-16 10:38       ` Robert Pluim
2020-10-16 10:49         ` Eli Zaretskii
2020-10-16 19:30         ` Alan Third
2020-10-17  6:38           ` Lars Ingebrigtsen
2020-10-17  9:12             ` Eli Zaretskii
2020-10-18  8:09               ` Lars Ingebrigtsen [this message]
2020-10-18 15:02                 ` Eli Zaretskii
2020-10-19  8:35                   ` Lars Ingebrigtsen
2020-10-17 15:27             ` Alan Third
2020-10-17 15:51               ` Alan Third
2020-10-17  6:44           ` Eli Zaretskii
2020-10-19 19:11             ` Robert Pluim
2020-10-16 14:49     ` Lars Ingebrigtsen
2020-10-19 10:56       ` Robert Pluim
2020-10-19 14:55         ` Eli Zaretskii
2020-10-19 18:34           ` Robert Pluim
2020-10-19 18:52             ` Eli Zaretskii
2020-10-19 19:00               ` Robert Pluim
2020-10-19 19:03               ` Stephen Berman
2020-10-19 19:46                 ` Eli Zaretskii
2020-10-19 22:00                   ` Stephen Berman
2020-10-20  2:35                     ` Eli Zaretskii
2020-10-20  7:33                       ` Robert Pluim
2020-10-20  8:58                         ` Robert Pluim
2020-10-20 14:28                           ` Eli Zaretskii
2020-10-20 14:41                             ` Robert Pluim
2020-10-19 19:03             ` Stefan Kangas
2020-10-19 19:32               ` Robert Pluim
2020-10-19 19:47               ` Eli Zaretskii
2021-11-06 19:00 ` Lars Ingebrigtsen

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=87lfg4klay.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=44020@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=eliz@gnu.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).