From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: two suggestions to \typesetbuffer
Date: Fri, 08 Nov 2013 19:11:59 +0100 [thread overview]
Message-ID: <527D296F.3060006@gmx.es> (raw)
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.
2. PDF file hasn’t been changed since previous complete compilation (md5
sum again).
3. Buffer content was correctly compiled in previous compilation.
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?
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 reply other threads:[~2013-11-08 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 18:11 Pablo Rodriguez [this message]
2013-11-08 22:39 ` Hans Hagen
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=527D296F.3060006@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).