From: Herbert Voss <Herbert.Voss@fu-berlin.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: luaotfload
Date: Fri, 12 Apr 2019 15:17:46 +0200 [thread overview]
Message-ID: <c66f066d-1baf-29a7-da50-79b7cfed10da@fu-berlin.de> (raw)
Hello all,
If I run the following document on a 8 GByte RAM Linux machine.
It takes more than 30 minutes until luaotfload has build
the cache for Sparks-Dotline-Medium.otf. If I run another
Program in the background that it never ends (too less memory).
On my Mac the first run with context (upcoming TL2019) needs 9.5 Gbyte
memory and nearly 100% CPU load to scan the Sparks-Dotline font.
This one is, of course, 400 kB big, but why do we need
more than 8 GByte Ram??
The font files are here:
http://tug.org/~hvoss/Sparks-Bar-Medium.otf
http://tug.org/~hvoss/Sparks-Dotline-Medium.otf
-rw-r--r-- 1 voss voss 34412 Apr 11 18:54 Sparks-Bar-Medium.otf
-rw-r--r-- 1 voss voss 403776 Apr 11 18:54 Sparks-Dotline-Medium.otf
\definefont[sparkBarMedium][file:Sparks-Bar-Medium.otf:mode=node;+calt]
\definefont[sparkDotlineMedium][file:Sparks-Dotline-Medium.otf:mode=node;+calt]
\starttext
Text
{\sparkBarMedium{14,95,68,9,19,41,91,1,81,97,79,45,96,76,17,65,8,92}} Text
Text
{\sparkDotlineMedium{14,95,68,9,19,41,91,1,81,97,79,45,96,76,17,65,8,92}}
Text
\stoptext
Herbert
___________________________________________________________________________________
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
___________________________________________________________________________________
next reply other threads:[~2019-04-12 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 13:17 Herbert Voss [this message]
2019-04-12 15:34 ` luaotfload Hans Hagen
2019-04-12 15:57 ` luaotfload Herbert Voss
2019-04-12 16:05 ` luaotfload Hans Hagen
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=c66f066d-1baf-29a7-da50-79b7cfed10da@fu-berlin.de \
--to=herbert.voss@fu-berlin.de \
--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).