From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, larsi@gnus.org, 57962@debbugs.gnu.org
Subject: bug#57962: 29.0.50; Odd font choices
Date: Mon, 17 Oct 2022 15:40:49 +0000 [thread overview]
Message-ID: <CADwFkmniSvdvuKRni1ofRkrf-HRFFf-FP--=1cGGiaVBiYcYFA@mail.gmail.com> (raw)
In-Reply-To: <83v8oi1pu2.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> AFAIK, an average browser comes with a fixed system-dependent list of
> fonts it uses for its various display parts, and doesn't allow users
> any freedom in determining typefaces of various display parts, except
> by replacing the fixed list of fonts by another fixed list. There's
> AFAIK nothing even close to Emacs's fontsets and faces.
>
> So the job of an average browser is much easier, and the freedom of
> its users is much smaller. IOW, we are trying to solve a much harder
> problem.
You can have arbitrary fonts in web browsers too, but it's true that
they are generally much less customizable (for the user) than Emacs.
They also usually don't have a block cursor to edit it all with, so they
get away with things that we might consider imperfections, such as
uneven line heights.
We might be veering off too far from the issue at hand though.
Sorry about that.
next prev parent reply other threads:[~2022-10-17 15:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 22:16 bug#57962: 29.0.50; Odd font choices Lars Ingebrigtsen
2022-09-21 2:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-21 10:43 ` Lars Ingebrigtsen
2022-10-14 11:41 ` Lars Ingebrigtsen
2022-10-14 11:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 12:02 ` Lars Ingebrigtsen
2022-10-14 12:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 12:13 ` Lars Ingebrigtsen
2022-10-14 12:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 12:07 ` Eli Zaretskii
2022-10-14 12:18 ` Lars Ingebrigtsen
2022-10-14 12:37 ` Eli Zaretskii
2022-10-14 12:48 ` Lars Ingebrigtsen
2022-10-14 13:00 ` Eli Zaretskii
2022-10-14 13:06 ` Lars Ingebrigtsen
2022-10-14 13:09 ` Eli Zaretskii
2022-10-16 10:58 ` Lars Ingebrigtsen
2022-10-16 11:17 ` Eli Zaretskii
2022-10-16 12:19 ` Lars Ingebrigtsen
2022-10-16 13:53 ` Eli Zaretskii
2022-10-17 9:57 ` Lars Ingebrigtsen
2022-10-17 10:22 ` Eli Zaretskii
2022-10-17 11:35 ` Lars Ingebrigtsen
2022-10-17 12:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-17 14:26 ` Eli Zaretskii
2022-10-17 14:20 ` Stefan Kangas
2022-10-17 14:34 ` Eli Zaretskii
2022-10-17 15:40 ` Stefan Kangas [this message]
2022-10-18 0:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkmniSvdvuKRni1ofRkrf-HRFFf-FP--=1cGGiaVBiYcYFA@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=57962@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.