ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz via ntg-context" <ntg-context@ntg.nl>
To: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
Cc: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: [NTG-context] fallbacks
Date: Sat, 22 Apr 2023 21:25:46 +0200	[thread overview]
Message-ID: <26633b3f-2ed1-4cec-d6f8-58819b2f9031@uni-bonn.de> (raw)
In-Reply-To: <144bd13a-b57d-97c7-cf2a-56fa7fe1ae15@gmx.es>

Thank you, Pablo, but that doesn't help. I know how to use fallback 
fonts. I was wondering if the check key is working as it should.

Thomas

On 4/22/23 20:33, Pablo Rodriguez via ntg-context wrote:
> Hi Thomas,
> 
> I don’t know what check does (maybe just check?), but the standard
> behaviour with \definefallbackfamily is only to fall back when the
> character is missing from the main font.
> 
> To force all characters from the range in the fallback font, "force=yes"
> is required.
> 
> Here you have a minimal sample (which doesn‘t use "preset=range:greek"),
> adding "force=yes" gets all Greek glyphs from GFS Heraklit:
> 
>    \definefallbackfamily [presentation] [serif] [GFSHeraklit]
>    [range={greekandcoptic, greekextended}]
>    \definefontfamily [presentation] [serif] [TeXGyrePagella]
>    \setupbodyfont [presentation,12pt]
> 
>    \starttext
>    Pπμᾷσδ
>    \stoptext
> 
> Just in case it might help,

-- 
Prof. Dr. Thomas A. Schmitz
Institut für Klassische und Romanische Philologie
Universität Bonn
Am Hof 1e
53113 Bonn
http://www.philologie.uni-bonn.de/de/personal/schmitz

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2023-04-22 19:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-22 16:05 Thomas A. Schmitz via ntg-context
2023-04-22 18:33 ` Pablo Rodriguez via ntg-context
2023-04-22 19:25   ` Thomas A. Schmitz via ntg-context [this message]
2023-04-25  5:46     ` Sylvain Hubert via ntg-context

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=26633b3f-2ed1-4cec-d6f8-58819b2f9031@uni-bonn.de \
    --to=ntg-context@ntg.nl \
    --cc=thomas.schmitz@uni-bonn.de \
    /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).