From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: ToC depth (and headers) per section block
Date: Sat, 05 Jul 2014 09:02:57 -0400 [thread overview]
Message-ID: <53B7F781.6070307@rik.users.panix.com> (raw)
In-Reply-To: <53B7C8BE.9060400@wxs.nl>
On 2014-07-05 05:43, Hans Hagen wrote:
> On 7/5/2014 5:52 AM, Rik Kabel wrote:
>> How can I specify different section depths for different parts in a
>> document in the TOC? That is, if the document structure is:
>>
>> Front Matter
>> Body Matter
>> Part 1
>> Chapter 1
>> Section 1
>> Chapter 2
>> Section 1
>> Section 2
>> Part 2
>> Chapter 1
>> Section 1
>> Section 2
>> Chapter 2
>> Section 1
>> Appendices
>> Chapter 1
>> Section 1
>> Chapter 2
>> Section 1
>> Back Matter
>> Notes
>> Bibliography
>>
>> How can I generate chapter and section entriess in the TOC for Part 1,
>> but chapter entries only (no section entries) for Part 2 and the
>> Appendices.
>>
>> I currently do this by defining a new header equivalent to section and
>> using that for Part 2 and Appendix sections. Since it is not included in
>> the lists used by the contents combinedlist, it does not get set.
>>
>> Is this the best way to do this?
>
> \definehead[silentsection][section]
>
> \starttext
>
> \placelist[chapter,section]
>
> \chapter{first}
> \section{first}
>
> \chapter{first}
> \silentsection{first}
>
> \stoptext
>
Yes, that is just what I do now, except that I use \completecontent and
not \placelist[chapter,section], having excluded lower-level sectioning
headers via \setupcombinedlist. I am asking if there is a way to take
advantage of user-defined or system modes, or section blocks, to
accomplish this without requiring explicit markup (silentsection in your
example) in the text. I suspect that it is possible, particularly if I
want the silentsections only in certain section blocks.
The document is set differently for print and screen, and minimizing the
differences after \starttext seems to me to be generally advantageous.
>> If instead I want one depth for all body matter parts and a different
>> depth for the appendices, is there a solution that could be keyed on
>> system modes or on section blocks, thus moving all of the styling to the
>> preamble (to use a LaTeX term)? I currently do that to support different
>> header formats in the body matter and appendices, using the following
>> method, but I suspect that there may be a more effective way to do that
>> as well.
>>
>> \startsetups [Header]
>> \startallmodes [print,*bodypart]
>> {\color[PrintHeaderColor]{\PrintHeaderFont
>> {\llap{\getmarking[chapternumber]~}\getmarking[chapter]}}
>> \stopallmodes
>> \startallmodes [print,*appendix]
>> \color[PrintHeaderColor]{\PrintHeaderFont
>> {\getmarking[chapter]}}
>> \stopallmodes
>> \stopsetups
>> \setupheadertexts []
>> \setupheadertexts [\setups{Header}][][][\setups{Header}]
>>
>> Again, I prefer a method that can be implemented in the preamble. (MKIV
>> only.)
>>
--
Rik Kabel
___________________________________________________________________________________
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:[~2014-07-05 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-05 3:52 Rik Kabel
2014-07-05 9:43 ` Hans Hagen
2014-07-05 13:02 ` Rik Kabel [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=53B7F781.6070307@rik.users.panix.com \
--to=context@rik.users.panix.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).