ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Carlos via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux
Date: Fri, 31 Mar 2023 22:22:49 +0200	[thread overview]
Message-ID: <da0a2e5d-7cde-b581-42ad-7099da5652fa@freedom.nl> (raw)
In-Reply-To: <20230331200807.hf2refl6kfsb3yrr@gmail.com>

On 3/31/2023 10:08 PM, Carlos via ntg-context wrote:

>> sure, why should it, you want lucida so better quit with an error than
>> kicking in some font; actually cmr math fonts have been obsoleted for way
>> over a decade by latin modern math fonts in 32 bit font engines

Font loading and processing time can be mosty neglected so these 16 
seconds come from something else, maybe there are ways to trace file 
access. Another possibility is that your fonts are not cached in which 
case every run will involve parsing the otf / ttf and producing whatever 
resources needed (normally cached).

> I was actually thinking to ask you about that, and by falling back to cmr math font that perhaps would expedite loading time along the way.

These fonts are small (only huge cjk fonts with tens of thousands of 
glyphs or fonts with hundreds of accumulated features might have some 
impact but even then not in the final embedding stage).

Whan talking fonts, enabling for instance expansion (hz) and protusion 
might increase runtime a little. In practice, enabling for instance 
synctex has a bigger imnpacts on performance than handling fonts.
  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
___________________________________________________________________________________

  reply	other threads:[~2023-03-31 20:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-25 19:55 Carlos via ntg-context
2023-03-25 20:26 ` Hans Hagen via ntg-context
2023-03-25 20:46   ` Carlos via ntg-context
2023-03-26 23:25   ` Carlos via ntg-context
2023-03-27 13:31   ` Carlos via ntg-context
2023-03-27 13:43     ` Hans Hagen via ntg-context
2023-03-28 17:05       ` Carlos via ntg-context
2023-03-28 22:48         ` Hans Hagen via ntg-context
2023-03-31 11:40           ` Carlos via ntg-context
2023-03-31 14:40             ` Hans Hagen via ntg-context
2023-03-31 20:08               ` Carlos via ntg-context
2023-03-31 20:22                 ` Hans Hagen via ntg-context [this message]
2023-04-01 21:21                   ` Carlos via ntg-context
2023-04-02  8:41                     ` Hans Hagen via ntg-context
2023-04-05  9:28                       ` Carlos via ntg-context
2023-03-25 20:45 ` Hans Hagen via ntg-context
2023-03-25 21:36   ` Carlos via ntg-context
2023-03-25 22:09     ` Hans Hagen via ntg-context
2023-03-25 22:42       ` Carlos via ntg-context
2023-03-26 11:04         ` Henning Hraban Ramm via ntg-context
2023-03-26 13:08           ` Carlos via ntg-context
2023-03-26 13:21             ` Hans Hagen via ntg-context
2023-03-26 19:50               ` Carlos via ntg-context
2023-03-26 23:38           ` Carlos 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=da0a2e5d-7cde-b581-42ad-7099da5652fa@freedom.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@freedom.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).