From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Stephen Gaito <stephen@perceptisys.co.uk>
Subject: Re: Parallelizing typesetting of large documents with lots of cross-references
Date: Thu, 3 Dec 2020 13:21:00 +0100 [thread overview]
Message-ID: <5f95564a-99e2-4a5e-2c5a-c5518272b857@xs4all.nl> (raw)
In-Reply-To: <20201203110434.03385f42@nn01>
On 12/3/2020 12:04 PM, Stephen Gaito wrote:
> - very large (1,000+ pages),
not that large, literate code is often verbatim so that doesn't take
much runtime either
> - highly cross-referenced documents,
ok, that demands runs
> - with embedded literate-programmed code (which needs
> concurrent compiling and execution),
you only need to process those snippets when something has changed and
there are ways in context to deal with that (like \typesetbuffer and
such which only processes when something changed between runs)
> - containing multiple MetaFun graphics,
those don't take time assuming effecitne metapost code
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2020-12-03 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 11:04 Stephen Gaito
2020-12-03 11:32 ` Taco Hoekwater
2020-12-03 12:21 ` Hans Hagen [this message]
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=5f95564a-99e2-4a5e-2c5a-c5518272b857@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=stephen@perceptisys.co.uk \
/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).