From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: what defines the font size?
Date: Tue, 16 Oct 2018 19:48:41 +0200 [thread overview]
Message-ID: <b39de8a7-41cf-2a72-b501-3415f8426a12@gmx.es> (raw)
In-Reply-To: <ufuv2fki1m4t.dlg@nililand.de>
On 10/15/18 10:02 PM, Ulrike Fischer wrote:
> Am Mon, 15 Oct 2018 21:21:32 +0200 schrieb Pablo Rodriguez:
>> [...]
>> If two fonts have the same size, I think there may be a dimension which
>> has the same length in both. Which one is this?
>
> None. The font decides about its size.
Many thanks for your clear statement, Ulrike.
Thomas Pinney explains why this might happen:
http://www.thomasphinney.com/2011/03/point-size/.
I cannot claim that I understand his explanation, but it seems that
there is something about the em quad, which might be something like:
\setupframed
[offset=none,
framecolor=red,
rulethickness=0.01pt,
width=12pt,
height=12pt]
\starttext
\startTEXpage[offset=1em]
\framed{M}
\framed{\tfxx M}
\framed{\tfd M}
\stopTEXpage
\stoptext
The square gives the points of the font (its size), but the glyphs might
be drawn in many different ways (I guess).
The issue with units per em is something I didn’t understand.
I tried to experiment (modifying TeX Gyre Pagella from 1000 to 9999
UPM), but for some reason, I wasn’t able to load the font.
Just in case anyone wonders, my code was standard:
\definefontfamily
[mainface]
[rm]
[TeX Gyre Pagella]
[bf=file:texgyrepagella-modified.otf]
\setupbodyfont[mainface]
And the file was on the same directory as my ConTeXt source file.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-10-16 17:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 19:21 Pablo Rodriguez
2018-10-15 20:02 ` Ulrike Fischer
2018-10-15 20:59 ` Hans Hagen
2018-10-16 7:07 ` Arthur Reutenauer
2018-10-16 7:35 ` Hans Hagen
2018-10-17 9:01 ` Ulrike Fischer
2018-10-16 17:50 ` Pablo Rodriguez
2018-10-16 20:52 ` Henning Hraban Ramm
2018-10-17 9:13 ` luigi scarso
2018-10-17 16:15 ` Pablo Rodriguez
2018-10-18 8:44 ` luigi scarso
2018-10-16 17:48 ` Pablo Rodriguez [this message]
2018-10-16 22:59 ` Hans Hagen
2018-10-17 15:59 ` Pablo Rodriguez
2018-10-17 9:02 ` Arthur Reutenauer
2018-10-17 16:14 ` Pablo Rodriguez
2018-10-17 17:05 ` Hans Hagen
2018-10-17 17:10 ` Alan Braslau
2018-10-17 17:13 ` Alan Braslau
2018-10-18 7:54 ` Arthur Reutenauer
2018-10-18 8:20 ` Hans Hagen
2018-10-19 6:24 ` luigi scarso
2018-10-19 8:15 ` Arthur Reutenauer
2018-10-22 19:10 ` Pablo Rodriguez
2018-10-18 8:37 ` Taco Hoekwater
2018-10-18 9:57 ` Hans Hagen
2018-10-18 16:38 ` Pablo Rodriguez
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=b39de8a7-41cf-2a72-b501-3415f8426a12@gmx.es \
--to=oinos@gmx.es \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).