From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: structure: project, product, structureresetset, ...
Date: Mon, 25 Mar 2013 18:45:12 +0100 [thread overview]
Message-ID: <3BBC3EB3-78C1-45F5-A8E5-036D4BEB8063@gmail.com> (raw)
In-Reply-To: <20130325162907.177508cb@sole>
Am 25.03.2013 um 16:29 schrieb Alan BRASLAU <alan.braslau@cea.fr>:
> Hello,
>
> I have a *project* that consists of a book in 3 volumes.
> Each volume is a *part*.
> Each volume or part has a (recto-verso) title page.
> Each volume or part also has front and back matter: table of contents, bibliography, index, ...
> Each volume or part also has *appendices*
>
> Thus, I have 3 *products* corresponding to the three volumes.
> Each product has *components*: chapters, appendices, ...
>
> Now, I would like the second volume to know that it is Part II and the third volume to know that it is Part III.
> I would also like to continue the chapter numbering in succession in each volume:
> i.e. 1, 2, 3 in Part I; 4, 5, 6 in Part II; 7, 8, 9 in Part III.
> Furthermore, I would like the appendices to do likewise:
> i.e. A, B in Part I; C, D, and E in Part II; F in Part III.
>
> Of course, I need to specify in my *environment*
>
> \definestructureresetset [default] [0,0] [1]
> \setuphead [part] [sectionresetset=default,conversion=Romannumerals]
>
> But... how do I propagate the numbering from product to product, that is part to part?
> Everything was just fine when all of the parts were collected into a single product
> having a unique front and back matter and all of the appendices at the end...
>
> It should be simple, but sometimes I fail to see the obvious! :)
\startsectionblockenvironment[bodypart]
\setupheadnumber[chapter][6]
\stopsectionblockenvironment
\startsectionblockenvironment[appendix]
\setupheadnumber[chapter][2]
\stopsectionblockenvironment
\starttext
\startbodymatter
\chapter{Chapter}
\stopbodymatter
\startappendices
\chapter{Appendix}
\stopappendices
\stoptext
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2013-03-25 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 15:29 Alan BRASLAU
2013-03-25 17:45 ` Wolfgang Schuster [this message]
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=3BBC3EB3-78C1-45F5-A8E5-036D4BEB8063@gmail.com \
--to=schuster.wolfgang@gmail.com \
--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).