From: Frank Steinmetzger <Warp_7@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] New monitor, new problem. Everything LARGE O_O
Date: Mon, 8 Jul 2024 22:21:19 +0200 [thread overview]
Message-ID: <ZoxKP302F37J55AD@kern> (raw)
In-Reply-To: <6062401.lOV4Wx5bFT@lenovo>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
Am Mon, Jul 08, 2024 at 06:26:26PM +0100 schrieb Michael:
> Back to the previous topic, I have not yet found a case where changing the
> scale by means of the desktop settings, arrives at non-blurred fonts. The
> clearest sharpest fonts are always rendered at the native monitor resolution,
> at a 100% scale setting. Am I missing a trick, or is this to be expected?
That doesn’t really make sense. Fonts are always rendered natively, no
matter what size. Except if they are really rendered at 100 % and then the
rendered bitmap is scaled by the GPU or somesuch.
Or because their hinting information is limited to a certain size range.
This info gives the renderer special knowledge on how to render the glyphs.
Do you have screenshots?
--
Grüße | Greetings | Salut | Qapla’
Please do not share anything from, with or about me on any social network.
One doesn’t eat salad, one feeds salat to one’s food.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-07-08 20:21 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 18:58 [gentoo-user] New monitor, new problem. Everything LARGE O_O Dale
2024-07-02 19:15 ` Michael
2024-07-02 19:35 ` Dale
2024-07-02 20:57 ` Mark Knecht
2024-07-06 9:59 ` Dale
2024-07-06 12:19 ` Michael
2024-07-06 16:11 ` Dale
2024-07-06 23:00 ` Michael
2024-07-07 0:32 ` Dale
2024-07-07 20:08 ` Frank Steinmetzger
2024-07-07 21:02 ` Wols Lists
2024-07-07 21:06 ` Mark Knecht
2024-07-07 21:23 ` Dale
2024-07-07 21:52 ` Fonts: was: " Jack
2024-07-09 8:43 ` [gentoo-user] Re: Fonts: was: " Nuno Silva
2024-07-07 22:12 ` [gentoo-user] " Frank Steinmetzger
2024-07-07 22:53 ` Dale
2024-07-07 23:16 ` Food was: " Jack
2024-07-07 23:47 ` Dale
2024-07-07 21:12 ` Dale
2024-07-07 21:26 ` Frank Steinmetzger
2024-07-07 22:10 ` Dale
2024-07-07 22:29 ` Frank Steinmetzger
2024-07-07 23:14 ` Wol
2024-07-08 9:57 ` Michael
2024-07-08 11:04 ` Wols Lists
2024-07-07 23:57 ` Dale
2024-07-08 10:48 ` Michael
2024-07-08 11:52 ` Wols Lists
2024-07-08 12:27 ` Dale
2024-07-08 12:59 ` Wol
2024-07-08 14:52 ` Peter Humphrey
2024-07-08 17:26 ` Michael
2024-07-08 20:21 ` Frank Steinmetzger [this message]
2024-07-08 23:02 ` Michael
2024-07-21 15:20 ` Frank Steinmetzger
2024-07-22 9:22 ` Michael
2024-07-08 17:59 ` Mark Knecht
2024-07-08 9:56 ` Michael
2024-07-08 14:55 ` Peter Humphrey
2024-07-02 21:53 ` Dale
2024-07-03 9:22 ` Dale
2024-07-03 14:53 ` Michael
2024-07-05 0:13 ` Dale
2024-07-10 5:00 ` Dale
2024-07-10 9:45 ` Michael
2024-07-10 11:44 ` Dale
2024-07-10 13:14 ` Michael
2024-07-11 6:23 ` Dale
2024-07-11 12:44 ` Michael
2024-07-14 5:08 ` Dale
2024-07-14 9:01 ` Michael
2024-07-14 9:44 ` Dale
2024-07-14 11:25 ` Michael
2024-07-14 15:25 ` Dale
2024-07-17 17:48 ` Dale
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=ZoxKP302F37J55AD@kern \
--to=warp_7@gmx.de \
--cc=gentoo-user@lists.gentoo.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