unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 46853@debbugs.gnu.org
Subject: bug#46853: Confusing terminology "face height" instead of "font size"
Date: Mon, 01 Mar 2021 19:06:14 +0200	[thread overview]
Message-ID: <835z2a952x.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=vsDvdEnmpo5BzBTTM=c-ETYHu3AxC-7ZSwT-pxvSK_A@mail.gmail.com> (message from Stefan Kangas on Mon, 1 Mar 2021 10:40:07 -0600)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Mon, 1 Mar 2021 10:40:07 -0600
> 
> I suggest changing the terminology "face height" to "font size" in user
> documentation and messages.  For example, the documentation for
> `text-scale-adjust' currently says:
> 
>    "Adjust the height of the default face by INC."
> 
> This is harder than it needs to be to understand, since the rest of the
> world actually talks about "increase font size".  IOW, it would be more
> clear if it said:
> 
>    "Adjust the font size in the current buffer by INC steps."

It's okay to make that change in this example, but one example is not
enough to understand what else is on the table.  How about showing a
patch, or at least the full list of places where you think we have
similar problems?  This should IMO be handled on a case by case basis
anyway.

> As part of this, we could also consider introducing a new property for
> `defface' called :size.  (Or :font-size and :font-scale which would
> allow for semantics where we can specify :font-size 14 and mean 14pt
> rather than 1.4pt.)

I wouldn't go that far; using :height is well established in Emacs
(and elsewhere, I believe: the face attributes were defined with XLFD
in mind).





  reply	other threads:[~2021-03-01 17:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01 16:40 bug#46853: Confusing terminology "face height" instead of "font size" Stefan Kangas
2021-03-01 17:06 ` Eli Zaretskii [this message]
2021-03-01 19:31   ` Stefan Kangas
2021-03-01 19:46     ` Eli Zaretskii
2021-03-01 17:12 ` Lars Ingebrigtsen
2021-03-01 17:17   ` Eli Zaretskii
2021-03-01 19:15   ` Stefan Kangas
2021-03-01 19:25     ` Lars Ingebrigtsen
2021-03-01 19:33       ` Lars Ingebrigtsen
2021-03-01 19:37         ` Lars Ingebrigtsen
2021-03-01 19:50           ` Eli Zaretskii
2021-03-01 19:48         ` Eli Zaretskii
2021-03-01 20:05           ` Lars Ingebrigtsen
2021-03-01 20:17             ` Eli Zaretskii
2021-03-03 22:43               ` Stefan Kangas
2021-03-04 13:41                 ` Eli Zaretskii
2021-03-04 18:05                   ` Stefan Kangas
2022-06-19 23:27             ` Lars Ingebrigtsen
2021-03-01 19:35       ` Eli Zaretskii
2021-03-01 19:45         ` Lars Ingebrigtsen
2021-03-01 19:59           ` Eli Zaretskii
2021-03-04  0:16             ` Stefan Kangas
2021-03-04 13:46               ` Eli Zaretskii
2021-03-04 17:35                 ` Stefan Kangas
2021-03-01 19:33     ` Eli Zaretskii

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=835z2a952x.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=46853@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    /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).