From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Herbert Voss <Herbert.Voss@fu-berlin.de>
Subject: Re: using variable font
Date: Thu, 1 Jul 2021 21:50:27 +0200 [thread overview]
Message-ID: <4b88677b-4316-1e3c-eba2-fdb04e9feed6@xs4all.nl> (raw)
In-Reply-To: <d767b8d2-fe1d-441f-028b-33cad16d855f@fu-berlin.de>
On 7/1/2021 9:19 AM, Herbert Voss wrote:
> Hello all,
>
> this worked years ago with another variable font. But it
> fails with FiraCode. I get always the same weight:
>
> \definefontfeature[w300][default][axis={weight:300}]
> \definefontfeature[w400][default][axis={weight:400}]
> \definefontfeature[w500][default][axis={weight:500}]
> \definefontfeature[w600][default][axis={weight:600}]
> \definefontfeature[w700][default][axis={weight:700}]
>
> \definefont [FiraCode@300] [file:FiraCode-VariableFont_wght.ttf*w300]
> \definefont [FiraCode@400] [file:FiraCode-VariableFont_wght.ttf*w400]
> \definefont [FiraCode@500] [file:FiraCode-VariableFont_wght.ttf*w500]
> \definefont [FiraCode@600] [file:FiraCode-VariableFont_wght.ttf*w600]
> \definefont [FiraCode@700] [file:FiraCode-VariableFont_wght.ttf*w700]
>
> \starttext
>
> \csname FiraCode@300\endcsname FiraCode, weight=300\par
> \csname FiraCode@400\endcsname FiraCode, weight=400\par
> \csname FiraCode@500\endcsname FiraCode, weight=500\par
> \csname FiraCode@600\endcsname FiraCode, weight=600\par
> \csname FiraCode@700\endcsname FiraCode, weight=700\par
>
> \stoptext
>
>
> the font is availabel at Google:
> https://fonts.google.com/specimen/Fira+Code
>
> It also fails with another variable font.
>
> up-to-date lmtx on macOS.
looks like a cache issue but there is also somethign else (with these
variable fonts one needs to run into an instance that actually uses one
of these fuzzy features)
i'll fix 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 / 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
___________________________________________________________________________________
prev parent reply other threads:[~2021-07-01 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 7:19 Herbert Voss
2021-07-01 19:50 ` Hans Hagen [this message]
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=4b88677b-4316-1e3c-eba2-fdb04e9feed6@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=Herbert.Voss@fu-berlin.de \
--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).