unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: larsi@gnus.org, maiku.fabian@gmail.com, 15420@debbugs.gnu.org
Subject: bug#15420: 24.3; Symbols like 🚴 (U+1F6B4) are not displayed by default
Date: Thu, 15 Aug 2019 18:40:09 +0300	[thread overview]
Message-ID: <83wofephd2.fsf@gnu.org> (raw)
In-Reply-To: <87sgq2h2w4.fsf@gmx.net> (message from Stephen Berman on Thu, 15 Aug 2019 17:19:55 +0200)

> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: Mike FABIAN <maiku.fabian@gmail.com>,  larsi@gnus.org,
>   15420@debbugs.gnu.org
> Date: Thu, 15 Aug 2019 17:19:55 +0200
> 
> > You will see in lisp/international/fontset.el that the #x1F680 --
> > #x1F6FF block is now configured to use Symbola by default, which is
> > why the BICYCLE and BICYCLIST are displayed without any changes.  As
> > for the Egyptian Hieroglyphs, we don't do anything about them,
> 
> Is this for technical reasons (e.g. redisplay speed) or a policy
> decision such as not enough free fonts?  I ask because e.g. Firefox
> seems to automatically find an installed font; for example, on my system
> Firefox displays the hieroglyphs on
> <https://en.wikipedia.org/wiki/Egyptian_Hieroglyphs_(Unicode_block)>,
> presumably using the Aegyptus fonts installed in my system, while EWW
> does not display the hieroglyphs (but does e.g. display the emoticons on
> <https://en.wikipedia.org/wiki/Emoticons_(Unicode_block)>, some using
> DejaVu, some using Symbola).

Firefox has a long list of known fonts stored in its database out of
the box.  We don't for 2 reasons: (1) we don't want to reference
non-free fonts, and (2) we want to be able to support the use case of
installing a font while the session runs.

The above may or may not be relevant to the Egyptian Hieroglyphs case;
volunteers are welcome to step through the font lookup process in
Emacs in that case and see whether we should add something to our
fontset-related databases.  After all, this script is quite rare, and
was added to Unicode at a relatively late date, so something might be
amiss.





  reply	other threads:[~2019-08-15 15:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-19 13:58 bug#15420: 24.3; Symbols like 🚴 (U+1F6B4) are not displayed by default Mike FABIAN
2019-08-15  3:42 ` Lars Ingebrigtsen
2019-08-15  9:01   ` Stephen Berman
2019-08-15  9:25     ` Mike FABIAN
2019-08-15 14:38       ` Eli Zaretskii
2019-08-15 15:19         ` Stephen Berman
2019-08-15 15:40           ` Eli Zaretskii [this message]
2019-08-17 13:50             ` Stephen Berman
2019-08-17 14:09               ` Eli Zaretskii
2019-08-17 14:56                 ` Stephen Berman
2019-08-17 15:03                   ` Eli Zaretskii
2019-09-29 13:53                     ` Lars Ingebrigtsen
2019-08-15 15:22     ` Eli Zaretskii

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=83wofephd2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=15420@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=maiku.fabian@gmail.com \
    --cc=stephen.berman@gmx.net \
    /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).