From: Yuri Khan <yuri.v.khan@gmail.com>
To: Oleksandr Gavenko <gavenkoa@gmail.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: Font selection algorithm / how do fonts work / what do you suggest for mono font?
Date: Mon, 26 Sep 2016 01:00:05 +0600 [thread overview]
Message-ID: <CAP_d_8WgWQ9EGibBk-KDJwdQ_QxyNTowRw+3Ms0jPDwmgD8jmg@mail.gmail.com> (raw)
In-Reply-To: <87twd46n3c.fsf@gavenkoa.example.com>
On Sun, Sep 25, 2016 at 10:00 PM, Oleksandr Gavenko <gavenkoa@gmail.com> wrote:
> Internet full of suggestion about font selection for programmers […]
>
> Most today recommendations end with vector fonts which is blurry and too bold
> to me.
>
> My current display has 95 DPI.
At 95 DPI, basically, you have a choice: either some amount of
blurriness, or some amount of corrupting the intended letter shape.
The knob is called hinting. Choose aggressive (“full”) hinting,
strokes are pulled to integer pixel coordinates, you get crisp ugly
letters. Choose slight hinting, letter shape is preserved as much as
practical, but some strokes will be at fractional coordinates and thus
blurry.
On a typical landscape-oriented monitor, vertical strokes can benefit
from subpixel hinting, although some call the result “rainbow soap”.
Both problems (blurriness and letter misshaping) pretty much disappear
at 2x pixel density or around 192 DPI. (However a new one appears —
you start to hate bitmap graphics, as it is either too blurry or too
small.)
prev parent reply other threads:[~2016-09-25 19:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-25 15:00 Font selection algorithm / how do fonts work / what do you suggest for mono font? Oleksandr Gavenko
2016-09-25 15:33 ` Eli Zaretskii
2016-09-25 19:04 ` Oleksandr Gavenko
2016-09-26 2:36 ` Eli Zaretskii
2016-09-26 21:07 ` Oleksandr Gavenko
2016-09-27 14:52 ` Eli Zaretskii
2016-09-25 16:13 ` Grant Rettke
2016-09-25 16:25 ` Eli Zaretskii
2016-09-25 19:00 ` Yuri Khan [this message]
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=CAP_d_8WgWQ9EGibBk-KDJwdQ_QxyNTowRw+3Ms0jPDwmgD8jmg@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=gavenkoa@gmail.com \
--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).