From: Werner LEMBERG <wl@gnu.org>
To: oub@mat.ucm.es
Cc: rogers@rgrjr.com, eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: has the emoji support been enhanced on master?
Date: Sun, 12 Feb 2023 12:14:03 +0000 (UTC) [thread overview]
Message-ID: <20230212.131403.246252144823988690.wl@gnu.org> (raw)
In-Reply-To: <87ilg7yxxi.fsf@mat.ucm.es>
>> ```
>>> sha256sum NotoColorEmoji.ttf
>> 060a297e16a27b69e5ef3080fa9900d8e60c875076b0be1cec7747f178c0dc5b NotoColorEmoji.ttf
>> ```
>
> Not the value I obtain
>
> sha256sum NotoColorEmoji.ttf
> 21fc478e003fc871200ba3bcf4215295a80e06a5c1b96f5368adc2183956f01a NotoColorEmoji.ttf
>
> Can you provide me a link with rpm?
According to `zypper --no-refresh se -s emoji` I have
'noto-coloremoji-fonts' version 20191119-1.9 from the main (openSUSE)
repository; the font identifies itself as version 2.02 (from
2019-10-16). Apparently, this package was retained while upgrading
from openSUSE 15.2 to 15.4 since there is no official package for
15.4.
Anyway, I've replaced the font with the current version available at
https://github.com/googlefonts/noto-emoji/blob/main/fonts/NotoColorEmoji.ttf
(font version 2.04 from 2022-09-20) and it works, too. I'm quite
convinced that the font version doesn't make a difference in solving
your problem.
Werner
next prev parent reply other threads:[~2023-02-12 12:14 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
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 [this message]
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=20230212.131403.246252144823988690.wl@gnu.org \
--to=wl@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=oub@mat.ucm.es \
--cc=rogers@rgrjr.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).