unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Vincent Lefevre <vincent@vinc17.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 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 08:47:14 +0100	[thread overview]
Message-ID: <20191118074714.GB27349@zira.vinc17.org> (raw)
In-Reply-To: <87ftinaq1h.fsf@gnus.org>

On 2019-11-17 09:02:50 +0100, Lars Ingebrigtsen wrote:
> Vincent Lefevre <vincent@vinc17.net> writes:
> 
> > For TrueType fonts, FreeType 2.8 uses different rounding rules for
> > values in the FT_Size_Metrics structure, which is apparently used
> > by Emacs (since there are visible changes). In particular, one can
> > now have ascender + descender > height. The consequences are:
> >
> > 1. Tables look a bit ugly.
> >
> > 2. Windows (with the same number of text lines) are unnecessarily
> >    higher than before.
> >
> > 3. This can break existing configurations, where Emacs would be
> >    opened at start up, with an expected window size.
> >
> > I could notice changes at least with the default Mono font, which
> > appears to be DejaVu Sans Mono.
> 
> The Emacs font rendering has changed some in Emacs 27 -- are you still
> seeing these problems there?

With a snapsnot from 23 August 2019,  I'm still seeing them.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)





  reply	other threads:[~2019-11-18  7:47 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 [this message]
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
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=20191118074714.GB27349@zira.vinc17.org \
    --to=vincent@vinc17.net \
    --cc=29078@debbugs.gnu.org \
    --cc=larsi@gnus.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).