ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Finding OSX fonts
Date: Fri, 14 Apr 2017 21:33:24 +0200	[thread overview]
Message-ID: <CD688EE6-82B6-4FC1-BB6F-D2EECA8FCD80@fiee.net> (raw)
In-Reply-To: <5B6ADF0C-298B-4C98-92FA-1F71955F7104@uva.nl>

Am 2017-04-14 um 20:58 schrieb Meer, Hans van der <H.vanderMeer@uva.nl>:

>> Did you refresh the database? 
>> i.e.
>> mtxrun --script font --reload
>> additionally try --force
>> 
> 
> The reload was necessary, indeed.
> Do I then correctly understand that the mtxrun --list call is searching the ConTeXt internal fontbase and not the macOS system directly, as I had (innocently) expected it was doing?

Exactly. If ConTeXt can’t find a font, it sometimes tries to refresh the database on its own (I don’t know under which circumstances), and that can take a while. The database access is much faster.
For my huge font collection, refreshing can take several minutes...

Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
GPG Key ID 1C9B22FD

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2017-04-14 19:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-14  9:38 Meer, Hans van der
2017-04-14 10:31 ` Henning Hraban Ramm
2017-04-14 12:43   ` Meer, Hans van der
2017-04-14 18:04     ` Henning Hraban Ramm
2017-04-14 18:58       ` Meer, Hans van der
2017-04-14 19:33         ` Henning Hraban Ramm [this message]
2017-04-14 22:15         ` Hans Hagen
2017-04-14 10:32 ` Hans Åberg

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=CD688EE6-82B6-4FC1-BB6F-D2EECA8FCD80@fiee.net \
    --to=texml@fiee.net \
    --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).