unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Juan José García-Ripoll" <juanjose.garciaripoll@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Font size innacuracies (Windows)
Date: Tue, 01 Mar 2022 16:48:29 +0100	[thread overview]
Message-ID: <86wnhd7jxu.fsf@csic.es> (raw)
In-Reply-To: 87k0ddithk.fsf@gmail.com

Same as if you put the pixel size in the name.

Robert Pluim <rpluim@gmail.com> writes:
>>>>>> On Tue, 01 Mar 2022 16:16:12 +0100, Juan José García-Ripoll
> <juanjose.garciaripoll@gmail.com> said:
>
>     Juan> I don't know. In principle the manual states that one can select pixels
>     Juan> in the name of the font, e.g. in set-frame-font. I tried it and changing
>     Juan> "Consolas:pixelsize=14" to "Consolas:pixelsize=12" does indeed change
>     Juan> the size.
>
>     Juan> In any case, what bothers me is that (i) even if Windows screws the
>     Juan> conversion, I do not find a suitable point or pixel size that matches
>     Juan> other applications (ii) the density of characters is different, both
>     Juan> vertically and horizontally, despite being monospaced fonts, (iii) the
>     Juan> difference in kerning and spacing is more remarked for variable-pitch
>     Juan> fonts.
>
> What happens if you use 'menu-set-font' instead?
>
> Robert

-- 
Juan José García Ripoll
http://juanjose.garciaripoll.com
http://quinfog.hbar.es




  reply	other threads:[~2022-03-01 15:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 10:24 Font size innacuracies (Windows) Juan José García-Ripoll
2022-03-01 14:21 ` Phillip Susi
2022-03-01 15:16   ` Juan José García-Ripoll
2022-03-01 15:26     ` Robert Pluim
2022-03-01 15:48       ` Juan José García-Ripoll [this message]
2022-03-01 17:14     ` Eli Zaretskii
2022-03-02  7:43       ` Juan José García-Ripoll
2022-03-02 20:06         ` Eli Zaretskii
2022-03-01 17:02 ` Eli Zaretskii
2022-03-02  7:19   ` Juan José García-Ripoll
2022-03-02 20:13     ` 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=86wnhd7jxu.fsf@csic.es \
    --to=juanjose.garciaripoll@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).