From: Hans Hagen <j.hagen@xs4all.nl>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Adobe Source Typescript With Design Sizes
Date: Fri, 3 Nov 2023 09:31:46 +0100 [thread overview]
Message-ID: <6769cae4-8cc4-4cd0-b816-1bc0059a6a82@xs4all.nl> (raw)
In-Reply-To: <a1573bec-1b45-4cc7-939e-808b9e098cf2@gmail.com>
On 11/2/2023 9:00 PM, Vincent Hennebert wrote:
> Ok. But then that means that the designsizes table will be used all the
> time, including when design sizes are disabled, right? Which would mean
> that I _must_ define the regular size as a fallback.
they are not really design sizes but more 'designed for s specific
purpose like display' .. so typesetting a 16 pt bodyfont in display is
not a good idea ... otherwise, if someone watched the text on a beamer
you'd have to use the display variant for everything as that definitely
goes over 10pt
> I think I see your point. I think we can still talk about design sizes
> but, instead of thinking in absolute sizes, we would want to think in
> sizes relative to the font setup.
indeed, and even more abstract: running text vs headings vs title pages
> That is, instead of saying ‘Caption shall be used for sizes 6.5pt and
> below, SmText for 9.5pt and below etc.’, we would want to say ‘Caption
> shall be used for 50% of the body font size and below, SmText for 75%
> and below, etc.’
i'm not sure what captions are for
> This way, design sizes would be used ‘harmoniously’ no matter the
> scaling. A poster, for instance, would usually be viewed at such a
> distance that the apparent size of small text (typeset at, say, 25pt
> when the main text is at 50pt, therefore using Caption) would match the
> apparent size of caption text in a regular document typeset at 12pt and
> read from a normal distance.
>
> Make sense?
posters stil can use regular but with a screaming bolder and darker
looking title in display (although often display doesn't look that good)
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 / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2023-11-03 8:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 19:18 [NTG-context] " Vincent Hennebert
2023-11-01 11:36 ` [NTG-context] " Hans Hagen via ntg-context
2023-11-02 20:00 ` Vincent Hennebert
2023-11-03 8:31 ` Hans Hagen [this message]
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=6769cae4-8cc4-4cd0-b816-1bc0059a6a82@xs4all.nl \
--to=j.hagen@xs4all.nl \
--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).