unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Torsten Bronger <bronger@physik.rwth-aachen.de>
To: help-gnu-emacs@gnu.org
Subject: Re: pgtk does not do subpixel rendering
Date: Fri, 13 May 2022 12:25:39 +0200	[thread overview]
Message-ID: <87zgjlwwyk.fsf@physik.rwth-aachen.de> (raw)
In-Reply-To: 874k1tx2v1.fsf@yahoo.com

Hallöchen!

Po Lu writes:

> Torsten Bronger <bronger@physik.rwth-aachen.de> writes:
>
>> I indeed used a too old Emacs (the Git HEAD of 14th March).
>> However, the current HEAD exhibits the same behaviour for me: No
>> subpixel rendering under Wayland on a low-res display if I compile
>> with --with-pgtk, and subpixel rendering without --with-pgtk.
>
> What happens if you run Emacs under Xwayland?

Frankly, I don’t know how to check whether Emacs uses Xwayland.  If
I compile with --with-x I would expect it to do always, but is this
the case?

> And are you sure that what you see is really because subpixel
> anti-aliasing is not being performed, and not because your hinting
> preferences are not being respected?

What I do is pretty crude: I make a screenshot and look at it in
Gimp heavily magnified.  With pgtk, I see only greyscale at the rim
of the glyphs, and without pgtk, I see pixels of various colours
(greenish/reddish).  This coincides with my subjective observation
that in the latter case, the text is crisper.

I do see subpixels in the menu text of other applications as well as
in the Chromium browser, in the same Gnome session as Emacs.

Regards,
Torsten.

-- 
Torsten Bronger




  reply	other threads:[~2022-05-13 10:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12 16:48 pgtk does not do subpixel rendering Torsten Bronger
2022-05-13  0:30 ` Po Lu
2022-05-13  7:46   ` Torsten Bronger
2022-05-13  8:18     ` Po Lu
2022-05-13 10:25       ` Torsten Bronger [this message]
2022-05-13 11:13         ` Po Lu
2022-05-13 12:06           ` Torsten Bronger
2022-05-15  8:08             ` Po Lu
2022-05-15 15:27               ` Torsten Bronger
2022-05-16  1:04                 ` Po Lu

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=87zgjlwwyk.fsf@physik.rwth-aachen.de \
    --to=bronger@physik.rwth-aachen.de \
    --cc=help-gnu-emacs@gnu.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.
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).