From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Richard Stallman <rms@gnu.org>
Cc: 41747@debbugs.gnu.org
Subject: bug#41747: 27.0.91; Add default fontset setup for "Symbols and Pictographs Extended-A"
Date: Wed, 10 Jun 2020 10:36:44 +0200 [thread overview]
Message-ID: <87wo4fz59f.fsf@gmail.com> (raw)
In-Reply-To: <E1jiozZ-0005E4-U7@fencepost.gnu.org> (Richard Stallman's message of "Tue, 09 Jun 2020 20:53:21 -0400")
Richard Stallman <rms@gnu.org> writes:
> However, it would be good to show the community that we are looking for
> people to design free repacements for those nonfree font extensions.
> I will discuss the issue with someone that works on free fonts.
NB: as highlighted earlier in the thread[1], there already are some free
fonts covering the newer characters.
They are color fonts though, so I don't think it would make sense to use
them just for "Symbols and Pictographs Extended-A": I expect users would
find it jarring if Emacs displayed emoji from this specific block with a
color font, yet displayed all others with a "regular"[2] font.
IMO the best way forward would be to consult Unicode's emoji list[3],
and enrich setup-default-fontset by iterating over every range and
(set-fontset-font "fontset-default" range
'("Noto Color Emoji" . "iso10646-1") nil 'prepend)
The (somewhat) complicated part is listing all ranges; it's not clear to
me yet if we want to do this manually, at compile-time, or once per
Unicode release, using scripts under admin/.
[1] <871rmpclzf.fsf@gmail.com>
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=41747#22
[2] Non-color? Black? Monochrome? 😕
[3] https://www.unicode.org/Public/UCD/latest/ucd/emoji/emoji-data.txt
next prev parent reply other threads:[~2020-06-10 8:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 13:43 bug#41747: 27.0.91; Add default fontset setup for "Symbols and Pictographs Extended-A" Kévin Le Gouguec
2020-06-07 13:47 ` Kévin Le Gouguec
2020-06-07 14:39 ` Eli Zaretskii
2020-06-07 15:22 ` Kévin Le Gouguec
2020-06-08 14:36 ` Eli Zaretskii
2020-06-08 20:59 ` Kévin Le Gouguec
2020-06-09 2:38 ` Richard Stallman
2020-06-09 9:58 ` Kévin Le Gouguec
2020-06-09 14:35 ` Eli Zaretskii
2020-06-10 0:53 ` Richard Stallman
2020-06-10 8:36 ` Kévin Le Gouguec [this message]
2020-06-10 14:48 ` Eli Zaretskii
2020-06-11 20:58 ` Alan Third
2020-06-11 21:03 ` Alan Third
2020-06-10 14:38 ` Eli Zaretskii
2020-06-11 3:40 ` Richard Stallman
2020-06-09 14:19 ` Eli Zaretskii
2020-06-09 2:35 ` Richard Stallman
2020-06-09 9:27 ` Kévin Le Gouguec
2020-06-09 14:41 ` Eli Zaretskii
2020-06-10 0:55 ` Richard Stallman
2020-06-10 8:50 ` Kévin Le Gouguec
2020-06-11 3:36 ` Richard Stallman
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=87wo4fz59f.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=41747@debbugs.gnu.org \
--cc=rms@gnu.org \
/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).