From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: two suggestions to \typesetbuffer
Date: Fri, 08 Nov 2013 23:39:31 +0100 [thread overview]
Message-ID: <527D6823.20209@wxs.nl> (raw)
In-Reply-To: <527D296F.3060006@gmx.es>
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)
> 2. PDF file hasn’t been changed since previous complete compilation (md5
> sum again).
takes time so less to gain there
> 3. Buffer content was correctly compiled in previous compilation.
define correctly
> 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
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-11-08 22:39 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 [this message]
2013-11-09 11:49 ` Pablo Rodriguez
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=527D6823.20209@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).