unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: has the emoji support been enhanced on master?
Date: Sat, 11 Feb 2023 19:40:20 +0200	[thread overview]
Message-ID: <83ttzshzi3.fsf@gnu.org> (raw)
In-Reply-To: <871qmwru41.fsf@mat.ucm.es> (message from Uwe Brauer on Sat, 11 Feb 2023 18:26:38 +0100)

> From: Uwe Brauer <oub@mat.ucm.es>
> Cc: Uwe Brauer <oub@mat.ucm.es>, emacs-devel@gnu.org
> Date: Sat, 11 Feb 2023 18:26:38 +0100
> 
> > And what does Emacs say for the "good" Emoji?
> 
> > In general, Unifont is the wrong font for displaying Emoji.  (IMNSHO,
> > it's the wrong font to display anything, so my suggestion is to
> > uninstall it from your system.)  Emacs is supposed to pick up a better
> > font, assuming it is installed.
> Well for ;) the winking one:
> 
> 
>              position: 5262 of 5263 (100%), column: 0
>             character: 😉 (displayed as 😉) (codepoint 128521, #o373011, #x1f609)
>               charset: unicode (Unicode (ISO10646))
> code point in charset: 0x1F609
>                script: emoji
>                syntax: w 	which means: word
>              category: .:Base
>              to input: type "C-x 8 RET 1f609" or "C-x 8 RET WINKING FACE"
>           buffer code: #xF0 #x9F #x98 #x89
>             file code: #xF0 #x9F #x98 #x89 (encoded by coding system utf-8-unix)
>               display: by this font (glyph code):
>     ftcrhb:-Free-Symbola-regular-normal-semicondensed-*-21-*-*-*-*-0-iso10646-1 (#x1BE8)

OK, I think I understand the problem: you don't have the Noto Color
Emoji font installed.  Install it, and the display will be according
to expectations.



  reply	other threads:[~2023-02-11 17:40 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11 14:39 has the emoji support been enhanced on master? Uwe Brauer
2023-02-11 15:31 ` Eli Zaretskii
2023-02-11 16:13   ` Uwe Brauer
2023-02-11 16:32     ` Eli Zaretskii
2023-02-11 17:06       ` Uwe Brauer
2023-02-11 17:13         ` Eli Zaretskii
2023-02-11 17:26           ` Uwe Brauer
2023-02-11 17:40             ` Eli Zaretskii [this message]
2023-02-11 19:17               ` Uwe Brauer
2023-02-11 19:21                 ` Eli Zaretskii
2023-02-11 19:38                   ` Uwe Brauer
2023-02-11 19:41                     ` Eli Zaretskii
2023-02-11 20:46                       ` Bob Rogers
2023-02-12  7:45                         ` Uwe Brauer
2023-02-12  8:05                           ` Eli Zaretskii
2023-02-12  9:26                             ` Uwe Brauer
2023-02-12 11:53                               ` Eli Zaretskii
2023-02-12 13:10                                 ` Uwe Brauer
2023-02-12 13:22                                   ` Eli Zaretskii
2023-02-12 20:19                                     ` Bob Rogers
2023-02-12 20:22                                       ` Eli Zaretskii
2023-02-12 20:44                                         ` Bob Rogers
2023-02-12  8:32                           ` Werner LEMBERG
2023-02-12  9:33                             ` Uwe Brauer
2023-02-12  9:59                               ` Werner LEMBERG
2023-02-12 10:34                                 ` Uwe Brauer
2023-02-12 12:14                                   ` Werner LEMBERG
2023-02-12 13:10                                     ` Uwe Brauer
2023-02-12 10:36                             ` Po Lu
2023-02-12 14:43                               ` Werner LEMBERG
2023-02-12 15:37                                 ` Po Lu
2023-02-12 16:56                               ` Benjamin Riefenstahl
2023-02-13  2:32                                 ` Po Lu
2023-02-13 14:25                                   ` Benjamin Riefenstahl
2023-02-13 15:08                                     ` Po Lu
2023-02-13 18:21                                       ` Benjamin Riefenstahl
2023-02-11 20:30                 ` Tim Cross

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=83ttzshzi3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=oub@mat.ucm.es \
    /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).