From: "Peter Münster" <pmlists@free.fr>
Subject: Re: Continuous chapter numbering
Date: Thu, 13 Oct 2005 23:10:33 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0510132302050.10695@gaston.free.fr> (raw)
In-Reply-To: <ba4316d30510131114v6a2c715fr2fc2d47905f1ecdb@mail.gmail.com>
On Thu, 13 Oct 2005, Randall Skelton wrote:
> I have a technical manual setup in ConTeXt whereby the manual itself is a
> ConTeXt 'project' and each chapter is a different component. Within this, I
> need to group some chapters together so these grouped chapters are products..
> Thus, I have:
>
> project: MyManual
> component: Chapter 1
> component: Chapter 2
> component: Chapter 3
> product: Example 1
> component: Chapter 4
> component: Chapter 5
> product: Example 2
> component: Chapter 6
> component: Chapter 7
> product: Example 3
> component: Chapter 8
> component: Chapter 9
Hello Randall,
it's considered, that the project-file contains only setup-commands and a
list of products, but no commands, that generate directly output.
When you compile a product, the referenced project-file gets included in
some manner, so every product of the project will inherit the same setups.
Compiling the project-file is seldom useful. It will generate all products
in one file.
Consider just, that one product is one document, and a component is a kind
of "sub-document" for example a chapter. And the project-file is just a
list of documents, that should inherit some common setups.
I suggest the following structure:
project: MyManual
product: the manual
component: Chapter 1
component: Chapter 2
component: Chapter 3
component: Chapter 4
component: Chapter 5
component: Chapter 6
component: Chapter 7
component: Chapter 8
component: Chapter 9
product: Example 1
component: title page for example 1
component: Chapter 4
component: Chapter 5
product: Example 2
component: title page for example 2
component: Chapter 6
component: Chapter 7
product: Example 3
component: title page for example 3
component: Chapter 8
component: Chapter 9
I hope, this helps.
Cheers, Peter
--
http://pmrb.free.fr/contact/
next prev parent reply other threads:[~2005-10-13 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 18:14 Randall Skelton
2005-10-13 21:10 ` Peter Münster [this message]
2005-10-24 22:59 ` Hans Hagen Test
2005-10-25 0:53 ` Matthias Weber
2005-10-25 8:05 ` Hans Hagen Test
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=Pine.LNX.4.58.0510132302050.10695@gaston.free.fr \
--to=pmlists@free.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).