From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Carlos via ntg-context <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: Wed, 29 Mar 2023 00:48:53 +0200 [thread overview]
Message-ID: <d211e51a-abd7-30ed-ee67-dee83c9e0a3f@xs4all.nl> (raw)
In-Reply-To: <20230328170512.2jdyuvgwfb64mrdi@gmail.com>
On 3/28/2023 7:05 PM, Carlos via ntg-context wrote:
> On Mon, Mar 27, 2023 at 03:43:47PM +0200, Hans Hagen via ntg-context wrote:
>> On 3/27/2023 3:31 PM, Carlos via ntg-context wrote:
>>
>>> mkiv lua stats > loaded fonts: 4 files: latinmodern-math.otf, lmroman10-regular.otf, lucidabrightregular.ttf, lucidasansregular.ttf
>>
>> i admit never having seen lucida ttf files (but when opentype ttf files are
>> used with an afm file present then no map files are needed at all because
>> we're in wide font mode and encidings are ignored)
>>
>
> I hadn't either. But everything aligned and thought it was nice.
>
> You're right that loading a map file is not needed, but If you're concerned about afm files then bring these files over to the working directory, and then mtxrun --generate the same
>
> So yes. Even though the file was something like (intended originally to load the map file, correct?) but since the map file is no longer necessary then afm should suffice
>
> \starttypescript [serif] [lucida] [texnansi]
> \definefontsynonym[LucidaBrightDemiBold][texnansi-lucidabrightdemibold][encoding=texnansi]
> \definefontsynonym[LucidaBrightDemiItalic][texnansi-lucidabrightdemiitalic][encoding=texnansi]
> \definefontsynonym[LucidaBrightItalic][texnansi-lucidabrightitalic][encoding=texnansi]
> \definefontsynonym[LucidaBrightRegular][texnansi-lucidabrightregular][encoding=texnansi]
> \stoptypescript
these encodings only make sense with mkii (in which case the map file
tells pdftex if a ttf or pfb file is used)
in mkiv encodings are ignored, when a ttf/otf file is used no afm is
read, and when a pfb fils is used the afm is used (ligature adn kerning
info etc) but a wide font is assembled
(when a ttf is used the lucidaot typescript file can serve as example)
in mkxl we assume the otf files sold by TUG are used (recently the math
font was updated)
> and not with the file specification as in:
>
>
> \starttypescript [mylucidaserif] % or mylucidasans
> \definefontsynonym[LucidaBrightRegular] [file:LucidaBrightRegular]
> \definefontsynonym[LucidaBrightItalic] [file:LucidaBrightItalic]
> \definefontsynonym[LucidaBrightBold] [file:LucidaBrightDemiBold]
> \stoptypescript
>
> and \setups[font:fallback:serif:sans] wouldn't be needed either
>
> you'd end up with
in mkxl (lmtx)
\setupbodyfont[lucida]
will load open type definitions
> 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
so why not use lucida math fonts?
>>> mkiv lua stats > font engine: otf 3.133, afm 1.513, tfm 1.000, 12 instances, 5 shared in backend, 3 common vectors, 2 common hashes, load time 16.898 seconds
>> i assume that you don't get this 16 seconds load time each run
>
> You're correct. That's why you recommended to use otf first .
even with type one fonts 17 sec load time for a few fonts is not okay, i
expect more something like:
mkiv lua stats > loaded fonts: 3 files: lucidabrightmathot.otf,
lucidabrightot.otf, lucidasansot.otf
mkiv lua stats > font engine: otf 3.133, afm 1.513, tfm 1.000, 14
instances, 10 shared in backend, 6 common vectors, 4 common hashes, load
time 0.161 seconds
(so 100 times less load time here)
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
___________________________________________________________________________________
next prev parent reply other threads:[~2023-03-28 22:48 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 [this message]
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
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=d211e51a-abd7-30ed-ee67-dee83c9e0a3f@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).