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: two issues with variable fonts
Date: Sun, 4 Dec 2022 18:17:55 +0100 [thread overview]
Message-ID: <14b0e1b7-d9f1-432a-6bfb-0fd060f3bbfd@gmx.es> (raw)
In-Reply-To: <6f245ce7-c492-e36a-3b46-8d308643bd5d@xs4all.nl>
On 12/4/22 11:53, Hans Hagen via ntg-context wrote:
>> [...]
> i'll check if we can deal with tags instead of names as not all fonts
> have nice names for the axis defined (which might be why one ends up
> with all these predefined instances)
Many thanks for your reply, Hans.
Tags instead of names seems more consistent to me. At least when
comparing it with OpenType features. And I think that "optical size" was
the first key I see containing a space.
Many thank sfor your help,
Pablo
___________________________________________________________________________________
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-04 17: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
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 [this message]
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=14b0e1b7-d9f1-432a-6bfb-0fd060f3bbfd@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).