From: jbf via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: jbf <roma83537@gmail.com>
Subject: font question re U+00336
Date: Tue, 24 May 2022 10:30:59 +1000 [thread overview]
Message-ID: <a34abb75-5617-03d0-3d6f-9bd393d1a77b@gmail.com> (raw)
I wonder if someone can help me interpret this message in the log file
fonts > start missing characters:
/home/jbf/bin/context/tex/texmf/fonts/opentype/public/tex-gyre/texgyrepagella-regular.otf
fonts > 88 U+00336 ̶ COMBINING LONG STROKE OVERLAY
fonts > stop missing characters
My questions are as follows:
1. What does 88 mean here? 88 instances of this missing glyph? Page 88?
Or something else? or in other words, how might I discover where
something is missing from the original text?
2. Tex Gyre Pagella is normally a pretty handy typeface to use for me
because it has pretty much all the glyphs I normally need... except this
one obviously! Isn't it really just an en rule (or very similar to
such)? Or in other words, how do I best overcome the problem of this
missing character?
3. And perhaps connected with the above question: is there good fallback
solution one can use? Do I need to \definefontfallback something or is
there an automatic one already happening?
I've started to examine the log files a bit more carefully for various
items and it is showing up my ignorance!!
Julian
___________________________________________________________________________________
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 reply other threads:[~2022-05-24 0:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 0:30 jbf via ntg-context [this message]
2022-05-24 7:26 ` Henning Hraban Ramm via ntg-context
2022-05-25 0:05 ` jbf 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=a34abb75-5617-03d0-3d6f-9bd393d1a77b@gmail.com \
--to=ntg-context@ntg.nl \
--cc=roma83537@gmail.com \
/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).