From: "Pablo Rodríguez" <oinos@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: isn't it too slow?
Date: Tue, 06 Dec 2011 22:07:25 +0100 [thread overview]
Message-ID: <4EDE840D.9000202@web.de> (raw)
In-Reply-To: <4EDE4DBB.8010000@wxs.nl>
On 12/06/2011 06:15 PM, Hans Hagen wrote:
> On 6-12-2011 13:22, Pablo Rodríguez wrote:
>> Hi there,
>>
>> compiling this minimal file:
>>
>> \definepapersize[aa][width=2cm,height=1cm]
>> \setuppapersize[aa]
>> \setuppagenumbering[location=]
>> \usemodule[simplefonts][size=12pt]
>> \definesimplefont[amsmile][TeX Gyre Pagella]
>> \starttext
>> \TeX\ \amsmile \TeX
>> \stoptext
>>
>> using
>>
>> This is LuaTeX, Version beta-0.70.1-2011061416 (rev 4277)
>> ConTeXt ver: 2011.05.18 18:04 MKIV fmt: 2011.8.1 int: english/english
>>
>> took
>>
>> system | total runtime: 144.057
>
> that can be because you ask for a font by name in which case the font
> name cache is regenerated ... so that happen seldom
>
>> Replacing the TeX Gyre Pagella font with small caps only takes
>>
>> system | total runtime: 6.753
>
> probably a first time caching of the font
When I update TeXLive 2011 invoking:
tlmgr update --self --all
after that I have to manually run:
mtxrun --script fonts --reload
if anything on the ConTeXt system has changed.
Otherwise, things like this happen every time I compile a ConTeXt document.
I guess there might be something wrong in tlmgr when updating ConTeXt,
but this is beyond my knowledge.
>> I guess something is wrong here, even if I'm doing something wrong.
>
> successive runs should be fast
If I don't regenerate the font cache as above, I get this mess every
time I compile a ConTeXt document invoking a system font by name.
Thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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:[~2011-12-06 21:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 12:22 Pablo Rodríguez
2011-12-06 13:30 ` Wolfgang Schuster
2011-12-06 14:55 ` Pablo Rodríguez
2011-12-06 17:14 ` Hans Hagen
2011-12-06 21:16 ` Pablo Rodríguez
2011-12-06 21:29 ` Wolfgang Schuster
2011-12-06 21:42 ` Hans Hagen
2011-12-07 18:18 ` Pablo Rodríguez
2011-12-06 17:15 ` Hans Hagen
2011-12-06 21:07 ` Pablo Rodríguez [this message]
2011-12-06 21:58 ` Idris Samawi Hamid ادريس سماوي حامد
2011-12-06 22:09 ` Hans Hagen
2011-12-07 18:35 ` Pablo Rodríguez
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=4EDE840D.9000202@web.de \
--to=oinos@web.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).