From: Alan BRASLAU <alan.braslau@cea.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Product-component structure
Date: Mon, 11 Jul 2016 08:42:11 -0600 [thread overview]
Message-ID: <20160711084211.31e7177d@cea.fr> (raw)
In-Reply-To: <op.ykfnlkg53h68c7@lpr>
On Mon, 11 Jul 2016 13:01:58 +0200
Procházka Lukáš Ing. <LPr@pontex.cz> wrote:
> - Single components can be compiled successfully, too; sections here
> are NOT NUMBERED as in the final document.
A nagging question that I have always had about structure is that it
would be rather nice if compiling a component that is part of a product
could use the .tuc information from an earlier compiling of the entire
product (if present) for numbering. Of course, modifying a component
(such as a chapter) might or would have an effect on all other
components of the product, but such is life.
In a large book product, working on a single chapter would be useful,
and getting the numbering at least close to correct is desirable.
Alan
___________________________________________________________________________________
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:[~2016-07-11 14:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 19:19 Aditya Mahajan
2016-06-24 22:20 ` Hans Hagen
2016-06-25 6:25 ` Wolfgang Schuster
2016-06-25 8:42 ` Aditya Mahajan
2016-06-25 9:56 ` Hans Hagen
2016-06-25 16:37 ` Aditya Mahajan
2016-06-25 17:10 ` Wolfgang Schuster
2016-06-25 17:24 ` Aditya Mahajan
2016-06-25 17:13 ` Wolfgang Schuster
2016-06-25 17:25 ` Aditya Mahajan
2016-07-11 11:01 ` Procházka Lukáš Ing.
2016-07-11 14:42 ` Alan BRASLAU [this message]
2016-06-26 9:34 ` 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=20160711084211.31e7177d@cea.fr \
--to=alan.braslau@cea.fr \
--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).