From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: what defines the font size?
Date: Tue, 16 Oct 2018 22:52:48 +0200 [thread overview]
Message-ID: <95B0909A-77CA-4802-A279-67C15BC07446@fiee.net> (raw)
In-Reply-To: <bae04470-c4eb-b9e7-83a1-8021feec4cdb@gmx.es>
Am 2018-10-16 um 19:50 schrieb Pablo Rodriguez <oinos@gmx.es>:
> On 10/15/18 10:59 PM, Hans Hagen wrote:
>>>> [...]
>>>> 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.
>> actually, the designer ... anyway, one can compare 10pt dejavu with 10pt
>> latin modern and 10pt lucida and you'll see that there is no real
>> standard in size
>
> Many thanks for your reply, Hans.
>
> I thought that I was missing something. For sure, but it was the
> explanation why there is no standarization in size.
Even in the times of lead type, there were differences in font size interpretation e.g. between Linotype and Berthold.
You could trust that the big vendors would handle their fonts alike, but printshops tried to avoid buying fonts from different vendors because they didn’t match.
Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD
___________________________________________________________________________________
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 20:52 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 [this message]
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
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=95B0909A-77CA-4802-A279-67C15BC07446@fiee.net \
--to=texml@fiee.net \
--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).