From: Alan Braslau via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Alan Braslau <alan.braslau@icloud.com>
Subject: Structure: multi-volume products
Date: Thu, 15 Dec 2022 20:23:36 -0700 [thread overview]
Message-ID: <20221215202336.059b1dc3@boo.my.domain> (raw)
Hello,
I have a book project that is being cut into two volumes (because it is
too long and will be sold as a boxed set).
Each volume is presently a separate *product* in the project structure.
I presently set the counters in the second volume using:
\setupheadnumber
[part] [2]
\setupheadnumber
[chapter] [5]
(I have multiple [5] parts in the project, and the first volume ends
with part 2 and chapter 5.)
1) Is this the right way to be handling this?
2) Any suggestions on how I can put a Table of Contents for the first
volume in the second volume?
Thanks!
Alan
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2022-12-16 3:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 3:23 Alan Braslau via ntg-context [this message]
2022-12-16 9:08 ` Denis Maier via ntg-context
2022-12-16 13:57 ` Alan Braslau via ntg-context
2022-12-16 13:59 ` Denis Maier via ntg-context
2022-12-16 14:01 ` Alan Braslau via ntg-context
2022-12-16 14:07 ` Denis Maier via ntg-context
2022-12-18 20:04 ` Alan Braslau via ntg-context
2022-12-16 9:31 ` Richard Mahoney | Indica et Buddhica via ntg-context
2022-12-16 13:59 ` Alan Braslau via ntg-context
2022-12-16 14:27 ` Alan Braslau via ntg-context
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=20221215202336.059b1dc3@boo.my.domain \
--to=ntg-context@ntg.nl \
--cc=alan.braslau@icloud.com \
/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).