From: Sylvain Hubert via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Sylvain Hubert <champignoom@gmail.com>
Subject: Re: [NTG-context] fallbacks
Date: Tue, 25 Apr 2023 13:46:26 +0800 [thread overview]
Message-ID: <CACNy3NBCCmdLD00a9hPKEcu3XWjG4hyDbkT8s38DAWy3wMP8aw@mail.gmail.com> (raw)
In-Reply-To: <26633b3f-2ed1-4cec-d6f8-58819b2f9031@uni-bonn.de>
[-- Attachment #1.1: Type: text/plain, Size: 2194 bytes --]
I believe it's a bug.
https://github.com/contextgarden/context/blob/d025bcdf995be6951f69fed6869048ab22491b9e/tex/context/base/mkxl/font-col.lmt#L278
the newchar[] table, which should contain all chars supported by the
fallback termes font if I'm not mistaken, turns out to have only 392 chars
within 0x20-0x30C, far away from 0x2329-0x232A.
On Sun, 23 Apr 2023 at 03:26, Thomas A. Schmitz via ntg-context <
ntg-context@ntg.nl> wrote:
> 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
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 3468 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2023-04-25 5:47 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
2023-04-25 5:46 ` Sylvain Hubert via ntg-context [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=CACNy3NBCCmdLD00a9hPKEcu3XWjG4hyDbkT8s38DAWy3wMP8aw@mail.gmail.com \
--to=ntg-context@ntg.nl \
--cc=champignoom@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).