From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: accessing ital axis in variable font
Date: Thu, 1 Dec 2022 21:44:29 +0100 [thread overview]
Message-ID: <4d4825ad-ac5f-6053-0ff1-04373d8e166c@xs4all.nl> (raw)
In-Reply-To: <0bd39893-cdee-7d01-9e36-02aa345f4fae@gmx.es>
On 12/1/2022 7:54 PM, Pablo Rodriguez via ntg-context wrote:
> Dear list,
>
> using the Literata variable fonts from
> https://github.com/googlefonts/literata/tree/main/fonts/variable, I have
> the following source:
>
> \definefontfeature[myaxis][axis={weight=500, italic=1}]
> \definefontfamily[mainface][rm][Literata][features={default, myaxis}]
> \setupbodyfont[mainface]
> \starttext
> \input zapf\par
> \it\input zapf
> \stoptext
>
> Other axes than weight (and only when not invoked as 'wght') don’t work
> for me (using latest from 2022.12.01 13:05).
>
> I have used the following source (it seems to be a goodie from current
> latest):
>
> \usemodule[fonts-variable]
> \starttext
> \showfontvariations[font=file:literata-italic.ttf]
> \showfontvariations[font=file:literata.ttf]
> \stoptext
>
> It reports that the Literata fonts have three (design) axes: wght, opsz
> and ital. ital is only a design axis.
>
> As explained before, they don’t work for me. How can I access to the
> italic and the optical size axes?
there is no axis defined for italic (it's a design axis so that's
probably why you have two fonts one with italic in the name)
so, just forget about it
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-01 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 18:54 Pablo Rodriguez via ntg-context
2022-12-01 20:44 ` Hans Hagen via ntg-context [this message]
2022-12-02 17:20 ` Pablo Rodriguez via ntg-context
2022-12-02 18:18 ` Hans Hagen via ntg-context
2022-12-03 9:18 ` 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=4d4825ad-ac5f-6053-0ff1-04373d8e166c@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).