From: Alan Bowen <bowenalan03@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: latest standalone—lua error
Date: Fri, 30 Apr 2021 11:21:54 -0400 [thread overview]
Message-ID: <CAFMOkGW54+-2Wmf4AJSmDVKcrAf08GgjiH=15mpxjY2F-jcUHw@mail.gmail.com> (raw)
In-Reply-To: <3319f070-3bad-f93a-a61d-26f277456e90@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2638 bytes --]
Hi, Wolfgang—
The mwe is:
\definefontfamily[mainface][rm][STIX Two Text]
[protrusion=quality,
expansion=quality,
mode=node,
force=yes,
features={default, f:oldstyle},
]
]
\definefallbackfamily[mainface] [mm] [STIX Two Text]
[range=digitsnormal,
force=yes,
features=f:oldstyle]
\definefontfamily[mainface][mm][STIX Two Math]
\setupbodyfont[mainface, 20pt]
\starttext
Hello world!
123456789
\m{123456789}
\oldstyle{123456789}
\stoptext
The problem disappears if I remove either
\definefallbackfamily[mainface] [mm] [STIX Two Text]
[range=digitsnormal,
force=yes,
features=f:oldstyle]
or
\definefontfamily[mainface][mm][STIX Two Math]
But in neither case do I get oldstyle numerals.
Note too that, when I remove \definefontfamily[mainface][mm][STIX Two
Math], my log file has
mkiv lua stats > loaded fonts: 2 files: lmmono10-regular.otf,
lmroman10-regular.otf
with no mention of STIX Two Text.
Yet ConTeXt is aware of the STIX Two Math and STIX Two Text fonts.
WE had a power failure very recently. I wonder if that has screwed things
up.
Alan
On Fri, Apr 30, 2021 at 9:45 AM Wolfgang Schuster <
wolfgang.schuster.lists@gmail.com> wrote:
> Alan Bowen schrieb am 30.04.2021 um 13:19:
>
> Hi, Wolfgang—
>
> I copied all the fonts to a new document (file attached) and ran ConTeXt.
> The problem persists. The cause, I think, comes in the lines:
>
> \definefallbackfamily[mainface] [mm] [STIX Two Text]
> [range=digitsnormal,
> force=yes,
> features=f:oldstyle]
> which used to give me oldstyle numerals.
>
>
> I'm unable to reproduce the error with your example and most of the
> fallbacks are ignored because I don't have the fonts.
>
> To ensure there is no problem with the format and font database delete the
> cache and rebuild it:
>
> mtxrun --script cache --erase
> mtxrun --generate
>
> When this doesn't help you simplify your example. First remove one
> \definefallbackfamily at a time and afterwards remove \definefontfamily
> until the error disappears.
>
> Wolfgang
>
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 9920 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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 prev parent reply other threads:[~2021-04-30 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 16:29 Alan Bowen
2021-04-29 18:24 ` Wolfgang Schuster
2021-04-30 11:19 ` Alan Bowen
2021-04-30 13:44 ` Wolfgang Schuster
2021-04-30 15:21 ` Alan Bowen [this message]
2021-04-30 15:47 ` Alan Bowen
2021-04-30 15:57 ` Hans Hagen
2021-04-30 16:08 ` Hans Hagen
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='CAFMOkGW54+-2Wmf4AJSmDVKcrAf08GgjiH=15mpxjY2F-jcUHw@mail.gmail.com' \
--to=bowenalan03@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).