ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz via ntg-context" <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: [NTG-context] fallbacks
Date: Sat, 22 Apr 2023 18:05:35 +0200	[thread overview]
Message-ID: <5e3ec3c4-0701-f2b3-b703-ab7f6e3170b6@uni-bonn.de> (raw)

Hi all,

today, I was struggling with a fallback font I had defined, and I 
discovered that the key "check" doesn't work as I expected. Here's a 
small example:

\definefallbackfamily [presentation] [serif] [TeXGyreTermes] 
[range=0x2329-0x232A,check=yes]
\definefontfamily [presentation] [serif] [AntykwaTorunska]
\setupbodyfont [presentation,12pt]

\starttext

(〈P〉)

\stoptext

With this input, the two characters 〈 and 〉 are not typeset; in the log, 
I find

fonts           > checking > char 〈 (U+02329) in font 
'AntykwaTorunska-Regular' with id 1: missing
fonts           > checking > char 〉 (U+0232A) in font 
'AntykwaTorunska-Regular' with id 1: missing

If I have "check=no," the characters are taken from termes and replaced. 
I was under the impression that "check" should, well, check if the 
characters are not in the main font and fall back to the fallback font 
if they are not, but this doesn't appear to be the case. So what does 
"check" do? Or is this a bug?

Have a great weekend

Thomas
___________________________________________________________________________________
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 16:06 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 [this message]
2023-04-22 18:33 ` Pablo Rodriguez via ntg-context
2023-04-22 19:25   ` Thomas A. Schmitz via ntg-context
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=5e3ec3c4-0701-f2b3-b703-ab7f6e3170b6@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).