From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Werner LEMBERG <wl@gnu.org>
Cc: casouri@gmail.com, yuri.v.khan@gmail.com, emacs-devel@gnu.org,
yandros@gmail.com, juri@linkov.net
Subject: Re: High-res Customize icons
Date: Thu, 23 Apr 2020 11:07:42 -0400 [thread overview]
Message-ID: <c1106d45-ff94-3a3d-4f25-f20af962d085@gmail.com> (raw)
In-Reply-To: <83r1wecl04.fsf@gnu.org>
On 23/04/2020 10.52, Eli Zaretskii wrote:
> What other applications are known to come with their own fonts and
> install them into the global font space of the system? Is this
> considered a good practice?
It's a common practice for websites to come with their own fonts, but they are never installed in the global font space. Some text editors ship with their own fonts (e.g. the JetBrains family of editors), but there, too, these fonts are not installed globally.
next prev parent reply other threads:[~2020-04-23 15:07 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 19:47 High-res Customize icons Yuan Fu
2020-04-22 2:23 ` Eli Zaretskii
2020-04-22 2:37 ` Clément Pit-Claudel
2020-04-22 5:47 ` chad
2020-04-22 12:24 ` Yuan Fu
2020-04-22 12:41 ` Yuri Khan
2020-04-22 13:54 ` Yuan Fu
2020-04-22 21:12 ` Juri Linkov
2020-04-22 22:20 ` Yuan Fu
2020-04-23 4:11 ` Werner LEMBERG
2020-04-23 14:52 ` Eli Zaretskii
2020-04-23 15:07 ` Clément Pit-Claudel [this message]
2020-04-23 17:49 ` Werner LEMBERG
2020-04-23 19:27 ` Eli Zaretskii
2020-04-23 19:35 ` Yuan Fu
2020-04-23 19:40 ` Eli Zaretskii
2020-04-23 19:59 ` Yuan Fu
2020-04-23 23:02 ` chad
2020-04-24 6:30 ` Eli Zaretskii
2020-04-24 11:00 ` Dmitry Gutov
2020-04-23 23:23 ` chad
2020-04-24 7:18 ` Eli Zaretskii
2020-04-25 3:30 ` Richard Stallman
2020-04-25 7:02 ` Eli Zaretskii
2020-04-25 12:37 ` Clément Pit-Claudel
2020-04-25 13:56 ` Eli Zaretskii
2020-04-22 13:35 ` Eli Zaretskii
2020-04-22 17:09 ` chad
2020-04-22 17:36 ` Eli Zaretskii
2020-04-22 18:28 ` chad
2020-04-22 18:38 ` Eli Zaretskii
2020-04-22 19:19 ` Yuan Fu
2020-04-22 19:28 ` Eli Zaretskii
2020-04-22 20:38 ` Yuan Fu
2020-05-01 13:46 ` Eli Zaretskii
2020-10-22 15:33 ` Yuan Fu
2020-10-23 16:39 ` Yuan Fu
2020-10-23 18:08 ` Eli Zaretskii
2020-10-27 19:17 ` Yuan Fu
2020-10-27 19:27 ` Eli Zaretskii
2020-10-27 22:26 ` Alan Third
2020-10-27 23:09 ` Yuan Fu
2020-10-28 0:05 ` Alan Third
2020-10-28 1:22 ` YAMAMOTO Mitsuharu
2020-10-29 5:31 ` Yuan Fu
-- strict thread matches above, loose matches on Subject: below --
2020-04-23 7:14 ndame
2020-04-23 7:25 ` ndame
2020-04-23 10:06 ` Stefan Kangas
2020-04-23 14:07 ` Stefan Kangas
2020-04-23 14:11 ` Stefan Kangas
2020-04-23 14:39 ` Clément Pit-Claudel
2020-04-23 14:46 ` Lars Ingebrigtsen
2020-04-23 15:00 ` Clément Pit-Claudel
2020-04-23 15:44 ` Stefan Monnier
2020-04-23 19:14 ` Eli Zaretskii
2020-04-23 20:33 ` Stefan Monnier
2020-04-24 6:51 ` Eli Zaretskii
2020-04-24 13:06 ` Stefan Monnier
2020-04-24 13:36 ` Eli Zaretskii
2020-04-24 15:13 ` Stefan Monnier
2020-04-24 15:46 ` Eli Zaretskii
2020-04-23 15:15 ` Eli Zaretskii
2020-04-23 15:17 ` Lars Ingebrigtsen
2020-04-23 16:40 ` Yuan Fu
2020-04-23 15:09 ` Eli Zaretskii
2020-04-23 16:19 ` Stefan Kangas
2020-04-23 16:35 ` Stefan Kangas
2020-04-23 15:08 ` Eli Zaretskii
2020-04-23 15:49 ` Clément Pit-Claudel
2020-04-23 16:34 ` Stefan Kangas
2020-04-23 19:56 ` Clément Pit-Claudel
2020-04-23 19:12 ` Eli Zaretskii
2020-04-25 2:55 ` Clément Pit-Claudel
2020-04-25 7:03 ` Eli Zaretskii
2020-04-25 13:12 ` Clément Pit-Claudel
2020-04-25 13:18 ` Stefan Kangas
2020-04-24 12:05 ` Eli Zaretskii
2020-04-24 15:11 ` ndame
2020-04-24 15:45 ` Eli Zaretskii
2020-04-24 16:07 ` Stefan Monnier
2020-04-24 16:29 ` Eli Zaretskii
2020-04-25 3:38 ` Richard Stallman
2020-04-28 13:55 ` Robert Pluim
2020-04-28 14:38 ` Eli Zaretskii
2020-04-29 12:30 ` Robert Pluim
2020-04-29 14:00 ` Eli Zaretskii
2020-04-25 3:34 ` Richard Stallman
2020-04-25 6:39 ` 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=c1106d45-ff94-3a3d-4f25-f20af962d085@gmail.com \
--to=cpitclaudel@gmail.com \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=wl@gnu.org \
--cc=yandros@gmail.com \
--cc=yuri.v.khan@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).