From: jbf <roma83537@gmail.com>
To: Henning Hraban Ramm <texml@fiee.net>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: running head for TOC
Date: Tue, 19 Jan 2021 20:34:12 +1100 [thread overview]
Message-ID: <a823a7f8-e22b-ff98-b5bb-12c53776464b@gmail.com> (raw)
In-Reply-To: <E80BFA97-16CC-4641-B0C6-CB5AA5EDE5F3@fiee.net>
I had tried that - I tried:
\definehead
[tochead]
[chapter]
and of course combined list does not contain tochead, but chapter. But
what happens then is that the Table of Contents disappears altogether)
except for the actually head 'Table of Contents')!
On 19/1/21 8:23 pm, Henning Hraban Ramm wrote:
>
>> Am 19.01.2021 um 05:55 schrieb jbf <roma83537@gmail.com>:
>>
>> I have a very long Table of Contents (runs across five pages) and the author would like the running head on recto pages for this to be 'Table of Contents'.
>>
>> I am using the following to create the TOC head:
>>
>> \definehead
>> [tochead]
>> [title]
>>
>> \starttochead[title={Table of Contents}]
>> \setupheader[state=start]
>> \placecombinedlist[content]
>> \stoptochead
>>
>> And I use the following to set up the headertexts for the book as a whole:
>>
>> \setupheadertexts
>> [{\hfill\getmarking[chapter]\hfill}][] %recto pages
>> [{\hfill\documentvariable{metadata:title}\hfill}][] %verso pages
>>
>> The problem is that I am unable to get 'Table of Contents' as a running head for the two recto pages where I need it. I realise I need to get 'tochead' recognised somehow for this. If I set up a separate \setupheadertexts [{\hfill\getmarking[tochead]\hfill}][] then I end up with 'Table of Contents as the running head on all recto pages, which I don't want.
>>
>> Can anyone suggest how can I get 'Table of Contents' as the running head just for the two recto pages of a five page TOC?
> How about you inherit "tochead" from "chapter" and setup the combined list "content" so that it doesn’t include "tochead"?
>
>
> Hraban
> ___________________________________________________________________________________
> 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://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2021-01-19 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 4:55 jbf
2021-01-19 9:23 ` Henning Hraban Ramm
2021-01-19 9:34 ` jbf [this message]
2021-01-19 19:11 ` Henning Hraban Ramm
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=a823a7f8-e22b-ff98-b5bb-12c53776464b@gmail.com \
--to=roma83537@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=texml@fiee.net \
/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).