ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Vincent Hennebert <vhennebert@gmail.com>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Optical scaling in Latin Modern
Date: Thu, 17 Aug 2023 12:02:36 +0200	[thread overview]
Message-ID: <e7308f88bf95d407e9e929332e435516016e2102.camel@gmail.com> (raw)
In-Reply-To: <6e72498a-20b1-45ce-3ff6-d9ff619f0e22@xs4all.nl>

On Tue, 2023-08-15 at 18:22 +0200, Hans Hagen wrote:

> On 8/15/2023 5:33 PM, Hamid,Idris wrote:
> 
> 
> > so [\s!designsize=\s!auto] means there is no explicit call to
lmroman8-regular etc.? Interesting..
> 
> 
> check the lfg file ...

On that note, there seems to be an inconsistency in the design size
selection:

    \setupbodyfont[modern-designsize,12pt]
    \starttext
    This text is typeset in LMRoman12.\par
    {\tfa This text should be typeset in LMRoman12 but LMRoman10
    is being used instead.}
    \stoptext

If I understand the font selection algorithm well, the font that will
be picked is the first font whose associated size is greater than or
equal to the requested size. If there is no such font the default is
used instead.

So, since in lm.lfg LMRoman12 is associated to 12pt, any text in a
higher size will be typeset using the default LMRoman10.

I understand that the default font should remain what it is since it
used when design sizes are disabled (using the typescript ‘modern’ and
not ‘modern-designsize’).

So, LMRoman12 should probably be associated to the biggest possible
value rather than 12pt (16383pt?).

Does that make sense?

Thanks,
Vincent


___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

      parent reply	other threads:[~2023-08-17 10:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 13:56 [NTG-context] " Hamid,Idris
2023-08-15 14:06 ` [NTG-context] " Hans Hagen
2023-08-15 14:35   ` Hamid,Idris
2023-08-15 14:56     ` Hans Hagen
2023-08-15 15:33       ` Hamid,Idris
2023-08-15 16:22         ` Hans Hagen
2023-08-16  0:48           ` Hamid,Idris
2023-08-17 10:02           ` Vincent Hennebert [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=e7308f88bf95d407e9e929332e435516016e2102.camel@gmail.com \
    --to=vhennebert@gmail.com \
    --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).