From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: issues with variable fonts in latest
Date: Thu, 15 Dec 2022 19:40:10 +0100 [thread overview]
Message-ID: <1667fee8-c6c6-92c0-0418-9110d5cac05e@gmx.es> (raw)
In-Reply-To: <69bfeb47-7423-8884-2d96-7adb0390a7ff@freedom.nl>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
On 12/15/22 17:39, Hans Hagen via ntg-context wrote:
> On 12/15/2022 5:00 PM, Pablo Rodriguez via ntg-context wrote:
>> Dear Hans,
>>
>> since you mentioned current latest (2022.12.09 16:34) regarding to
>> variable fonts today, I have found the following issues with Recursive
>> (comparing it with https://www.recursive.design/#toolbar):
> maybe old font cache content?
No, erased by hand and I attach the output from the just updated latest.
In red, I attach the results for 'mono=1', 'mono=1, casl=.75' and
'crsv=1' (from Inkscape).
Do you get the results in red with latest LMTX?
Many thanks for your help,
Pablo
[-- Attachment #2: recursive.pdf --]
[-- Type: application/pdf, Size: 14223 bytes --]
[-- Attachment #3: 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
___________________________________________________________________________________
next prev parent reply other threads:[~2022-12-15 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 16:00 Pablo Rodriguez via ntg-context
2022-12-15 16:39 ` Hans Hagen via ntg-context
2022-12-15 18:40 ` Pablo Rodriguez via ntg-context [this message]
2022-12-15 18:45 ` 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=1667fee8-c6c6-92c0-0418-9110d5cac05e@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).