From: Carlos via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Carlos <linguafalsa@gmail.com>
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: Tue, 28 Mar 2023 13:05:12 -0400 [thread overview]
Message-ID: <20230328170512.2jdyuvgwfb64mrdi@gmail.com> (raw)
In-Reply-To: <9fb9f0df-8798-4f03-abd2-f373585fc97c@freedom.nl>
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
\starttypescript [sans] [lucida] [texnansi]
\definefontsynonym[LucidaSansDemiBold][texnansi-lucidasansdemibold][encoding=texnansi]
\definefontsynonym[LucidaSansDemiOblique][texnansi-lucidasansdemioblique][encoding=texnansi]
\definefontsynonym[LucidaSansOblique][texnansi-lucidasansoblique][encoding=texnansi]
\definefontsynonym[LucidaSansRegular][texnansi-lucidasansregular][encoding=texnansi]
\stoptypescript
\starttypescript [mono] [lucida] [texnansi]
\definefontsynonym[LucidaSansTypewriterBold][texnansi-lucidatypewriterbold][encoding=texnansi]
\definefontsynonym[LucidaSansTypewriterBoldOblique][texnansi-lucidayypewriterboldoblique][encoding=texnansi]
\definefontsynonym[LucidaSansTypewriterOblique][texnansi-lucidatypewriteroblique][encoding=texnansi]
\definefontsynonym[LucidaSansTypewriterRegular][texnansi-lucidatypewriterregular][encoding=texnansi]
\stoptypescript
\starttypescript [serif] [lucida] [name]
\usetypescript[serif][fallback]
\definefontsynonym[Serif] [LucidaBrightRegular]
\definefontsynonym[SerifBold] [LucidaBrightDemi]
\definefontsynonym[SerifItalic] [LucidaBrightItalic]
\definefontsynonym[SerifBoldItalic][LucidaBrightDemiItalic]
\stoptypescript
\starttypescript [sans] [lucida] [name]
\usetypescript[sans][fallback]
\definefontsynonym[Sans] [LucidaSansRegular]
\definefontsynonym[SansItalic] [LucidaSansOblique]
\definefontsynonym[SansBold] [LucidaSansDemiBold]
\definefontsynonym[SansBoldItalic] [LucidaSansDemiOblique]
\stoptypescript
\starttypescript [mono] [lucida] [name]
\usetypescript[mono][fallback]
\definefontsynonym[Mono] [LucidaSansTypewriterRegular]
\definefontsynonym[MonoItalic] [LucidaSansTypewriterOblique]
\definefontsynonym[MonoBold] [LucidaSansTypewriterBold]
\definefontsynonym[MonoBoldItalic] [LucidaSansTypewriterBoldOblique]
\stoptypescript
\starttypescript [Lucida]
\definetypeface[MyLucida][rm][serif][lucida][default][encoding=texnansi]
\definetypeface[MyLucida][ss][sans][lucida][default][encoding=texnansi]
\definetypeface[MyLucida][tt][mono][lucida][default][encoding=texnansi]
\stoptypescript
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
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
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 0.306 seconds
mkiv lua stats > math tweaking time: 0.055 seconds, 12 math goodie tables
> > 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
> > mkiv lua stats > math tweaking time: 0.102 seconds, 12 math goodie tables
> > mkiv lua stats > font embedding time: 0.004 seconds, 2 fonts
>
> 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 .
>
> 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
> ___________________________________________________________________________________
--
Lisp Users:
Due to the holiday next Monday, there will be no garbage collection.
___________________________________________________________________________________
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 17:05 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 [this message]
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
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=20230328170512.2jdyuvgwfb64mrdi@gmail.com \
--to=ntg-context@ntg.nl \
--cc=linguafalsa@gmail.com \
/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).