From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: two suggestions to \typesetbuffer
Date: Sat, 09 Nov 2013 12:49:35 +0100 [thread overview]
Message-ID: <527E214F.70900@gmx.es> (raw)
In-Reply-To: <527D6823.20209@wxs.nl>
On 11/08/2013 11:39 PM, Hans Hagen wrote:
> On 11/8/2013 7:11 PM, Pablo Rodriguez wrote:
>> Dear Hans,
>>
>> I have presentations that include buffers typeset with \typesetbuffer.
>>
>> One of the presentation includes 33 buffers, which are small ConTeXt
>> samples.
>>
>> Any time I change anything on the presentation (not on the buffers
>> themselves), every buffer is typeset again. And the compilation time is
>> longer than probably desired.
>>
>> My first suggestion would be to skip compiling buffers again, if the
>> following three requirements are met:
>>
>> 1. Buffer content (.tmp file, I guess) is identical (checked with a
>> hash) with the previous one from last compilation.
>
> no temp file is used but a although a hash is possible it also means a
> lot of extra housekeeping due to the fact that buffers are reused (in
> which case no run happens)
Compiling the presentation I‘m talking about for the first time on my
laptop takes about 210 seconds. Every subsequent compilation takes about
70 seconds.
I know my laptop is old and slow.
But if I make a copy of the presentation source and remove the
\typesetbuffer commands, first compilation takes about 22 seconds and
subsequent compilations take about 7 seconds.
I have no idea on how ConTeXt works internally, but what I’m trying to
say is that if \typesetbuffer has been already compiled, compiling again
is no gain.
>> 3. Buffer content was correctly compiled in previous compilation.
>
> define correctly
I meant completely compiled: PDF has been generated.
>> My second suggestion may be a bit complex to implement, but I think it
>> would be useful. Wouldn’t it be possible that the fonts are only
>> embedded one in the presentation?
>
> how often does it happen ... if we're talking about one page files
> processing should normally fast e.g.
>
> \setupbodyfont[pagella] \starttext \input tufte \stoptext
>
> takes .3 seconds on my laptop.
>
> normally fonts are embedded efficiently (subsets) and shared
Sorry, there was a typo in my message: “that fonts are only embedded
once in the presentation”.
My second suggestion isn’t about compilation time, but about duplicated
fonts.
I tried to provide a sample, but I don’t know why it doesn’t work:
\starttext
These are bufers:
\dorecurse{10}{\startbuffer[text:\recurselevel]\setuppapersize[A7]\starttext\input
tufte\stoptext\stopbuffer\typesetbuffer[text:\recurselevel][frame=on]}
\stoptext
Of course, fonts are embedded fine in documents, but \typesetbuffer is a
special case. Having the fonts embedded only once in the final document
would be better.
Many 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:[~2013-11-09 11:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 18:11 Pablo Rodriguez
2013-11-08 22:39 ` Hans Hagen
2013-11-09 11:49 ` Pablo Rodriguez [this message]
2013-11-09 12:03 ` Wolfgang Schuster
2013-11-10 11:30 ` Hans Hagen
2013-11-10 12:32 ` Pablo Rodriguez
2013-11-10 15:29 ` 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=527E214F.70900@gmx.es \
--to=oinos@gmx.es \
--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).