ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Alan Braslau <braslau.list@comcast.net>
Subject: Re: \setupheadertexts \setupfootertexts
Date: Fri, 2 Aug 2019 21:08:00 +0200	[thread overview]
Message-ID: <e4652c50-56b8-83bb-058c-fddb3b32b90d@gmail.com> (raw)
In-Reply-To: <20190802122929.1a853a7e@poo.hsd1.co.comcast.net>

Alan Braslau schrieb am 02.08.2019 um 20:29:
> Hello,
>
> \setupheadertexts [{center}]
> sets a centered header (and wipes-out any left and right header)
>
> \setupheadertexts [{left}] [{right}]
> sets the left and right headers (and keeps the centered header)
>
> \setupheadertexts [{left odd}] [{right odd}] [{left even}] [{right even}]
> sets the left and right headers for even and odd pages
> (perhaps I have this backwards?)
>
>
>
> (1) It would be useful to have
> 	\setupheadertexts [{left}] [{center}] [{right}]
> but this does not work.
> In this case, we probably also need a *six* argument version (even/odd).
When you use three arguments the first is used for the position of text, 
i.e. above the text, margin or edge areas.

Only six or seven arguments work in this case but this only useful in a 
double sided document.
> (2) It would also be useful that
> 	\setupheadertexts [{center}]
> NOT wipe-out left and right if they are set
> (but I could live with this perhaps historical behavior if we were to have (1).)
>
> (3) It is a bit messy that one must use
> 	\setupheader []
> 	\setupheader [left] [right]
> *two calls* in order to have no centered header.
> (Again, I could live with
> 	\setupheader [left] [] [right]
> if we were to have (1).)
>
>
> Similarly for footertexts, of course.
> What is the reasoning, presently?
>
>
>
> ALTERNATIVELY (or additionally), we could have
>
> \setupheadertexts [center={center},
>                     left={left},
>                     lefteven={left, even},
>                     ...]
>
> which would be even cleaner.
You need a new command for this because adding an assignment option can 
produce unexpected results, e.g. the example below won't work anymore.

\setupheadertexts[{\date[d=...,m=...,y=...]}]

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
___________________________________________________________________________________

  reply	other threads:[~2019-08-02 19:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02 18:29 Alan Braslau
2019-08-02 19:08 ` Wolfgang Schuster [this message]
2019-08-02 20:26   ` Alan Braslau
2019-08-02 21:10     ` Hans Hagen
2019-08-02 21:36       ` Wolfgang Schuster
2019-08-02 21:59         ` Alan Braslau
2019-08-02 22:23           ` Hans Hagen
2019-08-02 22:31           ` Hans Hagen
2019-08-02 22:46         ` Hans Hagen

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=e4652c50-56b8-83bb-058c-fddb3b32b90d@gmail.com \
    --to=wolfgang.schuster.lists@gmail.com \
    --cc=braslau.list@comcast.net \
    --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).