ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Martin Schröder" <martin@oneiros.de>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: distributed / parallel TeX?
Date: Tue, 16 Dec 2008 22:31:18 +0100	[thread overview]
Message-ID: <68c491a60812161331h22bfd9e4rc69f508073d04269@mail.gmail.com> (raw)
In-Reply-To: <4947EFE6.6050302@sil.org>

2008/12/16 Lars Huttar <lars_huttar@sil.org>:
> - You could design your document *specifically* to make the parts
> independent, so that the true and authoritative way to typeset them is
> to typeset the parts independently. (You can do this part now without
> modifying TeX at all... you just have the various sections' .tex files
> input common "headers" / macro defs.) Then, by definition, a change in
> one section cannot affect another section (except for page numbers, and
> possibly left/right pages, q.v. below).

True. Also with TeX if your paragraphs are independent of each other
(i.e. they don't include references to others), they could the typeset
in parallel and then handed over to the page builder.

> - Most large works are divisible into chunks separated by page breaks
> and possibly page breaks that force a "recto". This greatly limits the
> effects that any section can have on another. The division ("chunking")
> of the whole document into fairly-separate parts could either be done
> manually, or if there are clear page breaks, automatically.

pdfTeX 1.50 knows about the page diversions (analogue to m4's divert
and undivert). They have a lot of potential.

> page number of each page reference. If pagination has changed, or is
> new, this info is sent back to the various nodes for another round of
> processing.

Hopefully stopping at some point. If you use something like varioref,
you can end with infinite circles. :-)

Best
   Martin
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-12-16 21:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-15 23:06 Lars Huttar
2008-12-16  8:08 ` Taco Hoekwater
2008-12-16 18:13   ` Lars Huttar
2008-12-16 21:31     ` Martin Schröder [this message]
2008-12-16 22:10       ` Lars Huttar
2008-12-16 22:17         ` Martin Schröder
2008-12-17  8:47           ` Taco Hoekwater
2008-12-16 21:15   ` luigi scarso
2008-12-16 23:02     ` Lars Huttar
2008-12-17  8:22       ` Hans Hagen
2008-12-17  8:53         ` luigi scarso
2008-12-17 13:50           ` Lars Huttar
2008-12-16  9:07 ` Hans Hagen
2008-12-16 15:06   ` Aditya Mahajan
2008-12-16 15:53     ` Hans Hagen
2008-12-16 17:25       ` Lars Huttar
2008-12-16 17:37         ` Hans Hagen
2008-12-16 19:28           ` Lars Huttar
2008-12-17  2:57             ` Yue Wang
2008-12-23  3:48             ` error when using uniqueMPgraphics Lars Huttar
2008-12-23  5:33               ` Lars Huttar
2008-12-23  7:30               ` Wolfgang Schuster
2008-12-16 18:40         ` distributed / parallel TeX? Mojca Miklavec

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=68c491a60812161331h22bfd9e4rc69f508073d04269@mail.gmail.com \
    --to=martin@oneiros.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).