From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: MacOsX Mavericks and Luatex
Date: Fri, 25 Oct 2013 07:13:00 +0900 [thread overview]
Message-ID: <52699B6C.6090401@wxs.nl> (raw)
In-Reply-To: <E52B7BE8-C421-421C-BDC4-F35674F8EA91@uni-bonn.de>
On 10/25/2013 7:01 AM, Schmitz Thomas A. wrote:
>
> On 24 Oct 2013, at 16:44, Aditya Mahajan <adityam@umich.edu> wrote:
>
>> You need to set it to a dummy directory! See: http://tex.stackexchange.com/a/136073/323
>
> No, even that doesn’t help:
>
> echo $OSFONTDIR
> /tmp/dummy
>
> and then on a first run (after regnerating the format with this variable set), I get lines such as
>
> fonts > names > 'OSFONTDIR' specifies path '/Users/tas/Library/Fonts'
> fonts > names > 'OSFONTDIR' specifies path '/Library/Fonts'
> fonts > names > 'OSFONTDIR' specifies path '/System/Library/Fonts'
> fonts > names > globbing path '/System/Library/Fonts/**.OTF'
> fonts > names > 68 system files identified, 2 skipped, 2 duplicates, 66 hash entries added, runtime 43.223 seconds
>
> So something appears to be overriding the variable that I set. But what? And why? And how do I stop it?
>
> On 24 Oct 2013, at 23:40, Hans Hagen <pragma@wxs.nl> wrote:
>
>> I don't understand the speed issue. We're talking about relatively few fonts only and context will not scan them unless there is a change. After a remake a rescan takes < 9 sec on my laptop and < 6 sec once the directories have been cached (windows 8 / 64 bit / i7 / ssd).
>>
>> Only an initial full scan takes a while (deleted cache), but that's mostly because I have a pretty large font collection in my texmf-fonts tree.
>
> You’re right of course that it’s only the initial run when a new font cache has to be built, but the time I get on os x is much longer than what you report:
>
> with rescanning of system fonts:
> system | total runtime: 114.131 (yes, that’s almost 2 minutes!)
>
> And I don’t want to twiddle my thumbs for two minutes, and don’t want to use those “system fonts” (or if I want to use them, I will copy them to my texmf directories)!
hm, i wonder why that takes so long as i get:
tex tree:
561 tree files identified, 5 skipped, 5 duplicates, 556 hash entries
added, runtime 14.282 seconds
426 tree files identified, 7 skipped, 5 duplicates, 419 hash entries
added, runtime 12.297 seconds
8 tree files identified, 0 skipped, 0 duplicates, 8 hash
entries added, runtime 0.188 seconds
0 tree files identified, 0 skipped, 0 duplicates, 0 hash
entries added, runtime 0.156 seconds
677 tree files identified, 1 skipped, 1 duplicates, 676 hash entries
added, runtime 0.672 seconds
system:
2 system files identified, 0 skipped, 0 duplicates, 2 hash
entries added, runtime 0.047 seconds
437 system files identified, 57 skipped, 57 duplicates, 380 hash entries
added, runtime 20.001 seconds
20 system files identified, 1 skipped, 1 duplicates, 19 hash
entries added, runtime 0.063 seconds
0 system files identified, 0 skipped, 0 duplicates, 0 hash
entries added, runtime 0.031 seconds
0 system files identified, 0 skipped, 0 duplicates, 0 hash
entries added, runtime 0.047 seconds
anyway, in a next beta you can set this in texmf.cnf.lua:
return {
content = {
directives = {
["fonts.usesystemfonts"] = false,
},
},
}
Best do that in texmf-local as a next update will overwrite the main cnf
file. Entries in the he local file overload main ones.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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 / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-10-24 22:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 5:41 Pierre Bovet
2013-10-24 6:03 ` Schmitz Thomas A.
2013-10-24 7:01 ` Schmitz Thomas A.
2013-10-24 7:12 ` Schmitz Thomas A.
2013-10-24 14:17 ` Hans Hagen
2013-10-24 14:28 ` Alan BRASLAU
2013-10-24 14:39 ` Schmitz Thomas A.
2013-10-24 14:44 ` Aditya Mahajan
2013-10-24 22:01 ` Schmitz Thomas A.
2013-10-24 22:13 ` Hans Hagen [this message]
2013-10-24 22:33 ` Aditya Mahajan
2013-10-25 7:30 ` Meer, H. van der
2016-05-19 14:26 ` MacOsX OSFONTDIR environment variable Meer, Hans van der
2013-10-24 21:40 ` MacOsX Mavericks and Luatex Hans Hagen
2013-10-24 7:04 ` Wolfgang Schuster
2013-10-24 7:13 ` Schmitz Thomas A.
2013-10-24 7:24 ` Wolfgang Schuster
2013-10-24 7:30 ` Pierre Bovet
2013-10-24 7:36 ` Wolfgang Schuster
2013-10-24 7:45 ` Pierre Bovet
2013-10-24 8:00 ` Wolfgang Schuster
2013-10-24 8:08 ` Schmitz Thomas A.
2013-10-24 8:31 ` Pierre Bovet
2013-10-24 9:56 ` Keith J. Schultz
2013-10-24 22:17 ` Hans Hagen
2013-10-25 8:49 ` Taco Hoekwater
2013-10-25 13:01 ` Otared Kavian
2013-10-24 9:13 ` Keith J. Schultz
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=52699B6C.6090401@wxs.nl \
--to=pragma@wxs.nl \
--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).