From: Pablo Rodriguez <oinos@gmx.es>
To: Hans Hagen via ntg-context <ntg-context@ntg.nl>
Subject: [NTG-context] Re: OSFONTDIR
Date: Thu, 20 Jul 2023 19:44:14 +0200 [thread overview]
Message-ID: <3a8bde96-cb10-eb8a-76cd-31869a7ce991@gmx.es> (raw)
In-Reply-To: <be90a3c9-aec5-d00e-0ba9-5e31f9417867@freedom.nl>
On 7/19/23 22:51, Hans Hagen via ntg-context wrote:
> On 7/19/2023 10:27 PM, Thomas A. Schmitz wrote:
>> [...] In the most recent versions of macos, some files of
>> these fonts are included as system fonts under
>> /System/Library/Fonts/Supplemental, but not all of them. It took me some
>> head scratching to figure out why every run complained about missing
>> glyphs until I saw that ConTeXt was using the wrong font. I had to set
>> the variable OSFONTDIR to some value to prevent this from happening. So
>> my question is: is looking for system fonts by default the new standard?
>> Is it a good idea?
>
> normally texmf-fonts is where i put fonts and that one should win
To solve this issues (since I use my private directory for fonts), I
created a symlink for my main font directory in $HOME/texmf/texmf-fonts/.
Before that, I had the symlink inside the LMTX distribution.
Just in case it might 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:[~2023-07-20 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 20:27 [NTG-context] OSFONTDIR Thomas A. Schmitz
2023-07-19 20:51 ` [NTG-context] OSFONTDIR Hans Hagen via ntg-context
2023-07-20 17:44 ` Pablo Rodriguez [this message]
2023-07-21 14:43 ` Alan Braslau via ntg-context
2023-07-21 14:48 ` Alan Braslau 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=3a8bde96-cb10-eb8a-76cd-31869a7ce991@gmx.es \
--to=oinos@gmx.es \
--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).