From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
mf <massifr@fastwebnet.it>
Subject: Re: new font trickery
Date: Wed, 23 Dec 2020 11:46:03 +0100 [thread overview]
Message-ID: <ad61d86d-5520-f3dd-0b0b-ffa2d875658a@xs4all.nl> (raw)
In-Reply-To: <d725f9bc-c3c1-d465-3775-d1fed30e9d30@fastwebnet.it>
On 12/23/2020 11:36 AM, mf wrote:
> When I started using ConTeXt, font management gave me headaches because
> I expected fonts to be indefinitely scalable and not to be designed in
> advance at fixed sizes.
>
> That came from using software like Word, where fonts are scalable at any
> size. Since I had no background in typesetting, I took vector,
> indefinitely scalable fonts for granted.
> With that mindset a 48pt font is just a 10pt font scaled 4.8 times.
>
> Then I knew about optical sizes, which were the norm with lead glyphs,
> because they came in heavy physical sets. And so the notion that as the
> font body gets bigger, the stroke gets thinner (so it's not just scaling).
>
> I like this feature because it should make playing with sizes easier for
> people while lighter for machines, even though fixed sizes to be
> designed in advance enforce discipline and consistency in documents.
Of course we can still keep the abstraction because we can define
sizes, think of:
\definescaledfont[bfe][xscale=2000,yscale=6000,style=bf]
(just made this feature work in two directions, not yet uploaded).
But you're right, we have to educate users in this.
Actually, I was wondering iif this could be abused to do vertical hz ...
filling a vbox / page with subtle scaling. It should be relatively easy
to implement, so when I'm bored ...
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2020-12-23 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 21:28 Hans Hagen
2020-12-23 10:36 ` mf
2020-12-23 10:46 ` Hans Hagen [this message]
2021-01-24 1:10 m-ipsum broken Jairo A. del Rio
2021-01-24 15:44 ` new font trickery Hans Hagen
2021-01-24 16:34 ` Pablo Rodriguez
[not found] ` <149c1645-b437-bc71-76f6-8ccd3bf1e650@xs4all.nl>
2021-01-24 17:16 ` Pablo Rodriguez
2021-01-24 21:25 ` Hans Hagen
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=ad61d86d-5520-f3dd-0b0b-ffa2d875658a@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=massifr@fastwebnet.it \
--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).