From: Sebastian Miele <sebastian.miele@gmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: 42240@debbugs.gnu.org
Subject: bug#42240: Interpretation of 'size' Property in Fontconfig Pattern Strings
Date: Thu, 16 Jul 2020 20:10:30 +0200 [thread overview]
Message-ID: <87r1tbib55.fsf@gmail.com> (raw)
In-Reply-To: <m2d04vs880.fsf@gmail.com>
Robert Pluim <rpluim@gmail.com>:
> Cairo implies --without-xft in any case, so no harm done.
Good to know. Thank you.
> Looks like Iʼll have to boot up my GNU/Linux box (although Iʼm hazy on
> the difference between 'size' and 'pixelsize')
The main Fontconfig manual page describing all properties is called 'man
5 fonts-conf' (which can be hard to find, because neither 'fc' nor
'fontconfig' are substrings of 'fonts-conf').
The 'size' is the point size. In general, there are many different
definitions of point size. But in practice only one is used nowadays
(except by TeX which uses a slightly different but very close definition
that works better with its fixed point arithmetics). Usually a point is
1/72 inch (https://en.wikipedia.org/wiki/Point_(typography)).
Together with 'dpi' (dots/pixels per inch) that defines the relation
between point size and pixel size.
X has at least two different places where a dpi may be defined. One for
the entire X display, although that does not really make sense with an X
display having monitors of different pixel densities. Apart from that at
least the Xrandr extension has a notion of distinct dpis per monitor.
In general, Fontconfig has an even separate dpi. I do not really know
what dpi Fontconfig uses, if it is not explicitly set in the Fontconfig
configuration, but, e.g.,
fc-match :family=Hack:size=11.1 size pixelsize dpi
or
fc-match -v :family=Hack:size=11.
display the dpi used.
next prev parent reply other threads:[~2020-07-16 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 11:25 bug#42240: Interpretation of 'size' Property in Fontconfig Pattern Strings Sebastian Miele
2020-07-16 15:03 ` Robert Pluim
2020-07-16 15:56 ` Sebastian Miele
2020-07-16 16:07 ` Sebastian Miele
2020-07-16 17:03 ` Robert Pluim
2020-07-16 18:10 ` Sebastian Miele [this message]
2020-07-16 18:11 ` Sebastian Miele
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=87r1tbib55.fsf@gmail.com \
--to=sebastian.miele@gmail.com \
--cc=42240@debbugs.gnu.org \
--cc=rpluim@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.