unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Daniele Nicolodi <daniele@grinta.net>, emacs-devel@gnu.org
Subject: Re: Increase default `line-spacing' to 0.05, 0.10 or 0.15 [proposal]
Date: Wed, 5 May 2021 14:17:01 -0500	[thread overview]
Message-ID: <CADwFkmmCiFEnRM8tJeQbhHH8RvEjKgHzphrK43FhLrte8VEY2g@mail.gmail.com> (raw)
In-Reply-To: <483dd6dd-d732-6f94-066f-9f07499ee430@grinta.net>

Daniele Nicolodi <daniele@grinta.net> writes:

>> C. A very conservative option is to use 0.05, which would be a small
>>    incremental improvement on what we already have. [58 lines, 3.33 %]
>>
>> D. The default. [60 lines, 0.0 %]
>
> On my system (macOS, Emacs 27.2 from https://emacsformacosx.com/) with
> some fonts, these two settings produce the same result. It seems that
> the "resolution" for this setting is 0.1 (thus 0.5 is rounded to 0.0).

I tested this on my macOS machine with a build from Homebrew, and one
built from the master branch.  In both these builds, 0.0 and 0.05 are
the same.  (0.1 and 0.15 are different, though.)

So I guess for this to matter on macOS, we would need to change this to
at least 0.1.

> In general, the visual distance between lines depends on the font: with
> some fonts I use a line-spacing of 0.0, while others require setting
> line-spacing to 0.15 to obtain roughly the same distance.

Yes, this will depend on the font.

Properly speaking, choosing the value should be a manual endeavor.  But
I don't think this is something we can easily do in Emacs as things
stand.  We would first need to build some infrastructure to change line
spacing depending on the font used.

Barring that, the best we can do is to find some happy average that
works okay most of the time.

    A true ideal line-height doesn’t exist, because every type-
    face is different.  You need to take into account the design of the
    typeface as well as the typesetting.  Is this a wide or decorative
    typeface?  You may need more space between lines to let the
    details breathe.  Is this a narrow text column, as you might see in
    hanging captions in an article’s margins?  You could use a smaller
    type size and keep the line-height tighter than the article text
    next to the caption.  By observing these factors, you can judge
    what a particular setting requires.

    A good starting point with line-height is about 1.2–1.8 ... It
    takes some trial and error to see what’s right for a given typeface
    at a given size in a given situation.  I find it useful to declare a
    line-height and see how it feels to read text at that setting.  Do
    letter ascenders and descenders crash into one another or run a
    little too close between lines? If so, more line-height is
    needed.  Are the spaces between the lines more prominent than the
    lines themselves?  If so, try reducing the line-height.  When you
    find an appropriate line-height, the text will seem to fall into a
    natural rhythm, feeling neither too far apart nor too close.

    - "On Web Typography", Jason Santa Maria, A Book Apart, 2014.



      reply	other threads:[~2021-05-05 19:17 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04 15:57 Increase default `line-spacing' to 0.05, 0.10 or 0.15 [proposal] Stefan Kangas
2021-05-04 16:12 ` Óscar Fuentes
2021-05-04 16:59   ` Jim Porter
2021-05-05  7:08     ` Augusto Stoffel
2021-05-05  8:51       ` Daniel Mendler
2021-05-05 19:47       ` Stefan Kangas
2021-05-06  9:26         ` Augusto Stoffel
2021-05-06 10:10           ` Eli Zaretskii
2021-05-06 11:47             ` Augusto Stoffel
2021-05-06 11:57               ` Eli Zaretskii
2021-05-06 12:27                 ` Augusto Stoffel
2021-05-06 15:21                   ` Eli Zaretskii
2021-05-06 15:46                     ` Augusto Stoffel
2021-05-06 16:16                       ` Eli Zaretskii
2021-05-06 12:30                 ` Gregory Heytings
2021-05-06 15:22                   ` Eli Zaretskii
2021-05-06 16:21                     ` Gregory Heytings
2021-05-06 16:29                       ` Eli Zaretskii
2021-05-06 16:57                         ` Daniele Nicolodi
2021-05-06 17:53                           ` Eli Zaretskii
2021-05-06 17:57                             ` Eli Zaretskii
2021-05-06 20:24                             ` Daniele Nicolodi
2021-05-06 17:01                         ` Gregory Heytings
2021-05-06 17:34                           ` Eli Zaretskii
2021-05-06 18:15                             ` Gregory Heytings
2021-05-06 20:22           ` Stefan Kangas
2021-05-06 20:21     ` Stefan Kangas
2021-05-06 23:17       ` Jim Porter
2021-05-07  6:03         ` Yuri Khan
2021-05-07  4:05       ` Eli Zaretskii
2021-05-04 16:18 ` Eli Zaretskii
2021-05-04 21:29   ` Stefan Kangas
2021-05-05  2:28     ` Eli Zaretskii
2021-05-05  5:14 ` Richard Stallman
2021-05-05 19:16   ` Stefan Kangas
2021-05-06 20:21     ` Stefan Kangas
2021-05-07  4:03       ` Eli Zaretskii
2021-05-07 18:43         ` Stefan Kangas
2021-05-08  6:19           ` Eli Zaretskii
2021-05-08  7:51             ` Daniele Nicolodi
2021-05-08  8:06               ` Eli Zaretskii
2021-05-08  9:40                 ` Daniele Nicolodi
2021-05-05 12:18 ` Daniele Nicolodi
2021-05-05 19:17   ` Stefan Kangas [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=CADwFkmmCiFEnRM8tJeQbhHH8RvEjKgHzphrK43FhLrte8VEY2g@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=daniele@grinta.net \
    --cc=emacs-devel@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.
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).