ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@xs4all.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: Sun, 2 Apr 2023 10:41:53 +0200	[thread overview]
Message-ID: <bd924912-a316-73e4-d02d-b5999701f290@xs4all.nl> (raw)
In-Reply-To: <20230401212151.b6cxllkzzuwot4nh@gmail.com>

On 4/1/2023 11:21 PM, Carlos via ntg-context wrote:
> On Fri, Mar 31, 2023 at 10:22:49PM +0200, Hans Hagen via ntg-context wrote:
>> 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).
> 
> interesting. Earlier as the output was showing
> 
>> mkiv lua stats  > loaded patterns: en::1, load time: 0.000
>> mkiv lua stats  > loaded fonts: 4 files: lucidabrightregular.otf, lucidasansregular.otf, latinmodern-math.otf, lmroman10-regular.otf
> 
> you asked
> 
>> so why not use lucida math fonts?
> 
> which is a valid question but nevertheless unsettling in that lmodern-regular may nat have been called out. I fully understand the inclusion of a latinmodern-math in it as a lucidamath was not previously available but I ponder at the idea and involuntary implementation  of having lmroman along the pack. Why? If this is TeX doings, or misdoings (depending how one looks at it), it clearly shows to me that TeX also restricts my freedom to use whatever font I may deem necessary. Don't you think? You can probably disagree with me here, or anyone from the TeX community can, but the roman last was imposed deliberately upon. Someoe may also give a lengthy explanation but that would be just hogwash in thee very end .

The fact that a file is loaded doesn't mean that it is used. In fact 
there is some fallback loading going on because explaining when nothing 
gets typeset or why \nullfont is used which results in missing chars 
messages is a waste of time.

It has nothing to do with restrictions: tex will load any font you want 
it. But for instance when you turn on some tracing the macro package can 
load a font it needs. Indirectly you get what you ask for.

I bet you didn't explicitly ask for e.g. english hyphentation patterns 
either but still got them, but tex will happily let you use polish ones 
instead.

Of course the best remedy against any automatism is to just start with 
initex and implement from scratch.

In the above case: just add \type {foo} and you might see another font 
you didn't ask for / set up.

>>> 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).
> 
> Yeah. I guess.
> 
> I can also have
> 
> mkiv lua stats  > loaded patterns: en::1, load time: 0.000
> mkiv lua stats  > loaded fonts: 3 files: lucidabrightmathsymbol.ttf, lucidanewmathitalic.ttf, lucidabrightregular.otf
> mkiv lua stats  > font engine: otf 3.133, afm 1.513, tfm 1.000, 6 instances, 3 shared in backend, 1 common vectors, 2 common hashes, load time 16.723 seconds
> 
> but that loading time gets back at me as the culprit sweet reminder of not using cmr then.

i won't comment because (i verified) that lucidabrightmathsymbol.ttf and 
  lucidanewmathitalic.ttf are illegal copies (if created on someones 
machine from the typeone its all up to that user).
  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-04-02  8:41 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
2023-04-01 21:21                   ` Carlos via ntg-context
2023-04-02  8:41                     ` Hans Hagen via ntg-context [this message]
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=bd924912-a316-73e4-d02d-b5999701f290@xs4all.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@xs4all.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).