From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: custom header/footer for 1st/other pages of section
Date: Tue, 11 Aug 2020 19:14:56 +0200 [thread overview]
Message-ID: <6f864c5c-308c-45a4-c5f7-0410063d9a43@gmail.com> (raw)
In-Reply-To: <BYAPR11MB2565FC40F5F1FF6AD9025DD3BD450@BYAPR11MB2565.namprd11.prod.outlook.com>
Mike Cooper schrieb am 11.08.2020 um 19:01:
>
>
>> -----Original Message-----
>> From: ntg-context [mailto:ntg-context-bounces@ntg.nl] On Behalf Of Henning
>> Hraban Ramm
>> Sent: Tuesday, August 11, 2020 12:37 AM
>> To: mailing list for ConTeXt users
>> Subject: Re: [NTG-context] custom header/footer for 1st/other pages of section
>>
>>> One thing I *CANNOT* figure out: I've been using \doifoddpageelse to put in a
>> blank/empty page at the end of a section (if needed) so that new sections always
>> start on an odd page. This is still working with the change to chapters from
>> sections, EXCEPT for the first chapter (after TOC)! Totally stuck with that one...
>>
>> Ehm... Why don’t you just use \setuphead[section][page=right] ?
>>
>> Hraban
>
>
> Haha! Well... because I never found that approach in my searching.
>
> But now, I'm not using it because it doesn't work for me. I was in the middle of guessing I needed to set up doublesided or some such in order for it to work when Wolfgang's other solution came in.
When you use "page=left" or "page=right" you need a doublesided document
but for a singlesided document you can use "page=even" or "page=odd".
There is also another layout method which combines both. The layout is
taken from a singlesided document which means the left and right margins
are the same on odd and even page but checks for left or right pages
work like in a doublesided document.
You can test this with the example below when you uncomment the second
and third pagenumbering setup-
\setuppagenumbering
[alternative={singlesided,doublesided}]
%\setuppagenumbering
% [alternative=singlesided]
%\setuppagenumbering
% [alternative=doublesided]
\setuphead
[chapter]
[page=right]
\showframe
\starttext
\dorecurse{3}
{\expanded{\chapter{Chapter \recurselevel}}
\dorecurse{4}{\samplefile{weisman}}}
\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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-08-11 17:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 15:15 Mike Cooper
2020-08-06 20:58 ` Wolfgang Schuster
2020-08-10 21:40 ` Mike Cooper
2020-08-11 6:37 ` Henning Hraban Ramm
2020-08-11 17:01 ` Mike Cooper
2020-08-11 17:14 ` Wolfgang Schuster [this message]
2020-08-11 17:45 ` Mike Cooper
2020-08-11 16:07 ` Wolfgang Schuster
2020-08-11 17:20 ` Mike Cooper
2020-08-11 18:06 ` Wolfgang Schuster
2020-08-20 17:37 ` Mike Cooper
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=6f864c5c-308c-45a4-c5f7-0410063d9a43@gmail.com \
--to=wolfgang.schuster.lists@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).