unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Vincent Lefevre <vincent@vinc17.net>
Cc: larsi@gnus.org, 29078@debbugs.gnu.org
Subject: bug#29078: 25.2; font issue with FreeType 2.8; should not use the rounded ascender and descender
Date: Mon, 18 Nov 2019 19:50:09 +0200	[thread overview]
Message-ID: <83lfsd2hwu.fsf@gnu.org> (raw)
In-Reply-To: <20191118172333.GE2742@cventin.lip.ens-lyon.fr> (message from Vincent Lefevre on Mon, 18 Nov 2019 18:23:33 +0100)

> Date: Mon, 18 Nov 2019 18:23:33 +0100
> From: Vincent Lefevre <vincent@vinc17.net>
> Cc: larsi@gnus.org, 29078@debbugs.gnu.org
> 
> AFAIK, from the font description (which does not involve rounding),
> there is no gap (that's why the FreeType developers suggested not
> to use the rounded values). Moreover, it does not make much sense
> to insert a gap. This looks ugly and this wastes screen space.

Emacs doesn't insert any gaps, it just computes the line metrics from
all the characters displayed on that line.

I've read the discussions of the FreeType developers, but couldn't
understand what they were talking about, as the discussion was in
terms of internals of FreeType, and I don't know enough to map that to
what the Emacs display engine does.

My point is that this seems to have nothing to do with the FreeType
library or its version, since I see the same on a system that uses
neither FreeType nor this particular font.  IOW, this looks to me
"normal", i.e. Emacs always worked like that.





  reply	other threads:[~2019-11-18 17:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 10:12 bug#29078: 25.2; font issue with FreeType 2.8; should not use the rounded ascender and descender Vincent Lefevre
2017-10-31 10:53 ` Robert Pluim
2017-10-31 11:22   ` Werner LEMBERG
2017-10-31 13:43     ` Vincent Lefevre
2017-10-31 15:45       ` Werner LEMBERG
2017-10-31 14:00     ` Robert Pluim
2017-10-31 16:24       ` Werner LEMBERG
2019-11-17  8:02 ` Lars Ingebrigtsen
2019-11-18  7:47   ` Vincent Lefevre
2019-11-18  8:30     ` Lars Ingebrigtsen
2019-11-18 16:05       ` Eli Zaretskii
2019-11-19 10:07         ` Robert Pluim
2019-11-19 11:34           ` Vincent Lefevre
2019-11-19 16:41             ` Stefan Kangas
2019-11-19 17:33               ` Eli Zaretskii
2019-11-18 15:36     ` Eli Zaretskii
2019-11-18 16:04       ` Vincent Lefevre
2019-11-18 17:09         ` Eli Zaretskii
2019-11-18 17:23           ` Vincent Lefevre
2019-11-18 17:50             ` Eli Zaretskii [this message]
2019-11-18 17:58               ` Eli Zaretskii
2019-11-18 18:20                 ` Vincent Lefevre
2019-11-18 18:31                   ` Eli Zaretskii
2019-11-18 18:15               ` Vincent Lefevre
2019-11-18 18:32         ` Lars Ingebrigtsen
2019-11-18 20:26           ` Vincent Lefevre
2019-11-18 20:31             ` Lars Ingebrigtsen
2019-11-19 15:55               ` 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=83lfsd2hwu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=29078@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=vincent@vinc17.net \
    /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).