ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Denis Maier via ntg-context <ntg-context@ntg.nl>
To: <alan.braslau@icloud.com>
Cc: denis.maier@unibe.ch, ntg-context@ntg.nl
Subject: Re: Structure: multi-volume products
Date: Fri, 16 Dec 2022 13:59:20 +0000	[thread overview]
Message-ID: <e4c61a2a3c30439eb981e06249d0d6c9@unibe.ch> (raw)
In-Reply-To: <20221216065744.2f3f011a@boo.my.domain>

What was his approach? Did he probably send it off-list?

> -----Ursprüngliche Nachricht-----
> Von: Alan Braslau <alan.braslau@icloud.com>
> Gesendet: Freitag, 16. Dezember 2022 14:58
> An: Maier, Denis Christian (UB) <denis.maier@unibe.ch>
> Cc: ntg-context@ntg.nl
> Betreff: Re: [NTG-context] Structure: multi-volume products
> 
> On Fri, 16 Dec 2022 09:08:47 +0000
> <denis.maier@unibe.ch> wrote:
> 
> > 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.
> 
> Thank you. This was my initial approach, although I know that ConTeXt can do
> better!
> 
> I will look into the suggestion sent by Richard Mahoney, as it looks like a good
> solution to the problem.
> 
> Alan
> 
> --
> Alan Braslau
> 816 West Mountain Avenue
> Fort Collins, CO 80521 USA
> mobile: (970) 237-0957
> 
> Conserve energy! ;-)
___________________________________________________________________________________
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 13:59 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
2022-12-16 13:57   ` Alan Braslau via ntg-context
2022-12-16 13:59     ` Denis Maier via ntg-context [this message]
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=e4c61a2a3c30439eb981e06249d0d6c9@unibe.ch \
    --to=ntg-context@ntg.nl \
    --cc=alan.braslau@icloud.com \
    --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).