From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 39340@debbugs.gnu.org, rpluim@gmail.com, ynyaaa@gmail.com
Subject: bug#39340: 26.3; "Noto Emoji" font not displayed
Date: Sun, 20 Sep 2020 12:55:54 +0200 [thread overview]
Message-ID: <878sd4pvid.fsf@gnus.org> (raw)
In-Reply-To: <83363c2054.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 20 Sep 2020 13:49:43 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> I'm not really sure what would we write in PROBLEMS. That some
> unnamed characters don't display correctly when HarfBuzz is not
> installed, and that if this happens, we suggest to install HarfBuzz
> and/or build Emacs with HarfBuzz support? If such a vague entry is
> deemed useful, I can write it.
Yeah, I think that would be useful.
> But note that build with HarfBuzz is nowadays the default, so the
> problem could happen only in rare corner use cases.
It should hopefully be something that few people trip over, but this bug
report is an example of that, so...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-09-20 10:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 4:12 bug#39340: 26.3; "Noto Emoji" font not displayed ynyaaa
2020-01-29 18:22 ` Eli Zaretskii
2020-01-30 5:13 ` ynyaaa
2020-01-30 14:38 ` Eli Zaretskii
2020-01-31 2:20 ` ynyaaa
2020-01-31 8:46 ` Eli Zaretskii
2020-01-31 10:43 ` Eli Zaretskii
2020-02-01 3:54 ` ynyaaa
2020-02-01 9:14 ` Eli Zaretskii
2020-02-01 11:52 ` YAGI Tatsuya
2020-02-01 12:46 ` Eli Zaretskii
2020-02-03 16:27 ` Robert Pluim
2020-02-03 16:58 ` Eli Zaretskii
2020-02-03 18:03 ` Robert Pluim
2020-02-03 18:22 ` Eli Zaretskii
2020-02-03 19:45 ` Robert Pluim
2020-02-03 19:57 ` Eli Zaretskii
2020-09-20 10:08 ` Lars Ingebrigtsen
2020-09-20 10:49 ` Eli Zaretskii
2020-09-20 10:55 ` Lars Ingebrigtsen [this message]
2020-09-20 11:09 ` Eli Zaretskii
2020-02-01 11:34 ` 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=878sd4pvid.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=39340@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rpluim@gmail.com \
--cc=ynyaaa@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).