ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Denis Maier via ntg-context <ntg-context@ntg.nl>
To: <ntg-context@ntg.nl>
Cc: denis.maier@unibe.ch
Subject: Re: Structure: multi-volume products
Date: Fri, 16 Dec 2022 09:08:47 +0000	[thread overview]
Message-ID: <e30979a51d5a4cf6bff80a4cc3412e8e@unibe.ch> (raw)
In-Reply-To: <20221215202336.059b1dc3@boo.my.domain>

Last time I had to do something like this I've kept both books in one master file (actually one master file for part 1, one for part 2, one for both together). With that I could easiliy have a table of contents for both volumes.

I've made some experiments with writing stuff to the logs or tuc file (\writestatus{SPLITPOINT}{\the\realpageno}) at the end of part 1, which I then wanted to process with a script (e.g., read the page number, use pdftk to split the complete PDF at this point to get PDFs for the individual volumes). However, at the end I've just had to send the PDF containing both volumes to the publisher as they performed the splitting up themselves.

Best,
Denis

> -----Ursprüngliche Nachricht-----
> Von: ntg-context <ntg-context-bounces@ntg.nl> Im Auftrag von Alan Braslau
> via ntg-context
> Gesendet: Freitag, 16. Dezember 2022 04:24
> An: mailing list for ConTeXt users <ntg-context@ntg.nl>
> Cc: Alan Braslau <alan.braslau@icloud.com>
> Betreff: [NTG-context] Structure: multi-volume products
> 
> 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
> ________________________________________________________________
> ___________________
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2022-12-16  9:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16  3:23 Alan Braslau via ntg-context
2022-12-16  9:08 ` Denis Maier via ntg-context [this message]
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=e30979a51d5a4cf6bff80a4cc3412e8e@unibe.ch \
    --to=ntg-context@ntg.nl \
    --cc=denis.maier@unibe.ch \
    /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).