unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Protesilaos Stavrou <info@protesilaos.com>
Cc: 53718@debbugs.gnu.org
Subject: bug#53718: 29.0.50; Recent change to font hinting in --with-pgtk build
Date: Wed, 02 Feb 2022 18:35:45 +0800	[thread overview]
Message-ID: <87iltxa73y.fsf@yahoo.com> (raw)
In-Reply-To: <87o83pk9uq.fsf@protesilaos.com> (Protesilaos Stavrou's message of "Wed, 02 Feb 2022 09:26:21 +0200")

Protesilaos Stavrou <info@protesilaos.com> writes:

> Dear maintainers,
>
> I built Emacs with commit 02054d9cd1f5c6a5ca3555207235522532477e10 using
> --with-pgtk and have noticed that there is a change to the hinting of
> the fonts relative to commit d25cb37694de446e6dd1095f489d5436ea9e20ae.
>
> Please refer to the attached screenshots which compare the two commits
> using Hack and Source Code Pro, respectively.  The differences are
> subtle, though you can see how the 'm' is affected.
>
> The hinting is inconsistent.  Even in this very message.  Notice the
> quotes in this 'Hack' with the one below which has a thinner first quote
> and thicker second one:
>
> 'Hack'
>
> All the best,
> Protesilaos

Thanks for reporting the bug.  Could it be a problem with your system?

Can you reproduce the problem with an X11 build with Cairo drawing?
Running configure without any arguments should produce such a build on
your system.

And please try bisecting to find exactly which commit caused the
problem.





  reply	other threads:[~2022-02-02 10:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02  7:26 bug#53718: 29.0.50; Recent change to font hinting in --with-pgtk build Protesilaos Stavrou
2022-02-02 10:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-07-06 11:42   ` Lars Ingebrigtsen
2022-07-06 12:04     ` Protesilaos Stavrou
2022-07-06 12:22       ` Lars Ingebrigtsen

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=87iltxa73y.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=53718@debbugs.gnu.org \
    --cc=info@protesilaos.com \
    --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 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).