From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: two issues with variable fonts
Date: Fri, 2 Dec 2022 20:17:10 +0100 [thread overview]
Message-ID: <ac3b5951-3591-cd97-50dd-10cc23c24374@freedom.nl> (raw)
In-Reply-To: <b3819803-7727-cdd2-40e2-317579a7cb8f@gmx.es>
On 12/2/2022 7:06 PM, Pablo Rodriguez via ntg-context wrote:
> Hi Hans,
>
> I have two issues with variable fonts (using current latest from yesterday):
>
> 1. Using the following sample:
>
> \usemodule[fonts-variable]
> \starttext
> \showfontvariations[font=file:grenze.ttf]
> \stoptext
>
> With the fonts from
> https://github.com/Omnibus-Type/Grenze/tree/master/fonts-/gx, I get the
> following error message:
>
> lua error:
> run callback [6]:
> ...ext/tex/texmf-context/tex/context/base/mkxl/lpdf-emb.lmt:84: number
> (local 'n') has no integer representation
> stack traceback:
> ...base/mkxl/lpdf-emb.lmt:84: in upvalue 'tocardinal2'
> ...base/mkxl/lpdf-emb.lmt:771: in local 'writer'
> ...base/mkxl/lpdf-emb.lmt:2358: in field 'integer index'
> ...base/mkxl/lpdf-ini.lmt:828: in upvalue 'run'
> ...base/mkxl/lpdf-ini.lmt:859: in field 'finalizedocument'
> ...base/mkxl/lpdf-lmt.lmt:3413: in field '?'
> ...base/mkxl/luat-run.lmt:58: in function
> <...ext/tex/texmf-context/tex/context/base/mkxl/luat-run.lmt:56>
>
> <empty file>
> mtx-context | fatal error: return code: 1
>
> This crashes LuaMetaTeX but not LuaTeX.
i'll catch it
> 2. The other font is Recursive
> (https://github.com/arrowtype/recursive/tree/main/fonts/recursive_for_googlefonts).
>
> \usemodule[fonts-variable]
> \starttext
> \showfontvariations[font=file:recursive.ttf]
> \stoptext
>
> There are some some instances (in pages 4 to 14) that don’t have the
> font (only Latin Modern Roman).
i'll catch it
> Also in the last instances (at least, pages 19 to 25), kerning or
> interletter spacing clearly needs to be improved.
no clue (ok, a little)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2022-12-02 19:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 18:06 Pablo Rodriguez via ntg-context
2022-12-02 19:17 ` Hans Hagen via ntg-context [this message]
2022-12-03 0:01 ` Hans Hagen via ntg-context
2022-12-03 9:29 ` Pablo Rodriguez via ntg-context
2022-12-04 10:53 ` Hans Hagen via ntg-context
2022-12-04 17:17 ` Pablo Rodriguez via ntg-context
2022-12-04 21:16 ` Henning Hraban Ramm via ntg-context
2022-12-06 18:56 ` Pablo Rodriguez via ntg-context
2022-12-06 20:07 ` Henning Hraban Ramm via ntg-context
2022-12-09 16:44 ` Pablo Rodriguez via ntg-context
2022-12-06 17:47 ` Pablo Rodriguez 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=ac3b5951-3591-cd97-50dd-10cc23c24374@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.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).