From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Aditya Mahajan <adityam@umich.edu>
Subject: Re: \definefontfamily not finding fonts
Date: Thu, 10 Sep 2020 20:40:04 +0200 [thread overview]
Message-ID: <54e381f0-6df2-415d-c9f6-11763daeb61e@xs4all.nl> (raw)
In-Reply-To: <nycvar.YAK.7.78.908.2009101210030.691510@nqv-guvaxcnq>
On 9/10/2020 6:20 PM, Aditya Mahajan wrote:
> On Thu, 10 Sep 2020, Wolfgang Schuster wrote:
>
>>>>> Any idea on what is going on and how to debug.
>>>> I can't reproduce your Libertinus problem but the sans serif and monospaced
>>>> fonts just use the wrong names.
>>> In by defense, it used to work for the last 5 years :-)
>>
>> Are you mixing \definetypeface and \definefontfamily?
>
> This is an old style and I understand that the current syntax is wrong. But it did work previously. But the correct syntax does not find the fonts either.
>
> Anyways, for now, I switched to typeface based interface
>
> \starttypescript[mainface]
> \definetypeface[mainface][rm][serif][libertine][default]
> \definetypeface[mainface][ss][sans] [heros] [default]
> \definetypeface[mainface][tt][mono] [dejavu] [default] [rscale=0.85]
> \definetypeface[mainface][mm][math] [libertine][default]
> \stoptypescript
>
> and it works correctly. So, it appears to be an issue with font name to filename mapping.
>
> I'll try a clean install on a docker image and check it that works ... or just wait for the newer version, which often fixes such things :-)
there have been no fundamental changes, but the names of these liber*
fonts change occasionally
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:[~2020-09-10 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 3:16 Aditya Mahajan
2020-09-10 7:40 ` Wolfgang Schuster
2020-09-10 15:53 ` Aditya Mahajan
2020-09-10 15:57 ` Wolfgang Schuster
2020-09-10 16:20 ` Aditya Mahajan
2020-09-10 18:40 ` 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=54e381f0-6df2-415d-c9f6-11763daeb61e@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=adityam@umich.edu \
--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).