From: jbf via ntg-context <ntg-context@ntg.nl>
To: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: jbf <roma83537@gmail.com>
Subject: Re: \setupheadertexts for chapters with different authors
Date: Sat, 19 Mar 2022 13:16:42 +1100 [thread overview]
Message-ID: <aa95fe62-eefe-f103-e292-68071c039e4a@gmail.com> (raw)
In-Reply-To: <49d83fe5-3310-30ac-79cc-26b88be47403@fiee.net>
[-- Attachment #1.1: Type: text/plain, Size: 1935 bytes --]
I might need a little more help just to understand how best to adapt
this to my situation:
One thing is clear: I was attempting to use a 'list' variable, and I can
see why that was an error, since it is headertexts, not TOC that I want
to influence.
But let me simplify my situation:
You seem to suggest initially that I could use \structureuservariable
(or \structurevariable) instead, especially since I already have a
variable to call on, e.g \startchapter[title={My title}][author={A.
uthor}]. But in the example you then gave, you made no use of either of
these.
My current setting is:
\setupheadertexts [{\hfill\getmarking[chapter]\hfill}][]
[{\hfill\documentvariable{metadata:title}\hfill}][]
which gives me the book title centred on verso pages, and the chapter
title centred on recto pages. All I want to do is to have the chapter
contributors' name for each chapter instead of the chapter title.
So why can't I create a setups along the lines of:
\startsetups[contributor] \getmarking[\structureuservariable{author}]
\stopsetups
Then just swap 'chapter' in \setupheadertexts, with 'contributor'? I
tried it but it doesn't work. I thought it would be logical. Clearly I'm
wrong but don't appreciate why.
Julian
On 18/3/22 18:52, Henning Hraban Ramm via ntg-context wrote:
> The *list* variables work only in lists.
>
> There’s also \structurevariable and \structureuservariable.
>
> Make sure you use setups for the header, otherwise the variable gets
> expanded only once at the beginning.
>
> Like in:
>
> \setuppagenumbering[alternative=doublesided]
> \setupheadertexts[] % empty
> \setupheadertexts[\setups{text right}][][][\setups{text left}]
>
> \startsetups[text right]
> \rlap{\pagenumber}
> \hfill
> \getmarking[chapter]
> \hfill
> \llap{Un Nom}
> \stopsetups
>
> \startsetups[text left]
> \rlap{Una Person}
> \hfill
> \getmarking[section]
> \hfill
> \llap{\pagenumber}
> \stopsetups
[-- Attachment #1.2: Type: text/html, Size: 2860 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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:[~2022-03-19 2:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 0:48 jbf via ntg-context
2022-03-18 7:52 ` Henning Hraban Ramm via ntg-context
2022-03-18 9:13 ` jbf via ntg-context
2022-03-18 10:49 ` Henning Hraban Ramm via ntg-context
2022-03-19 2:16 ` jbf via ntg-context [this message]
2022-03-19 2:55 ` jbf via ntg-context
2022-03-19 9:18 ` Henning Hraban Ramm via ntg-context
2022-03-19 9:32 ` Hans Hagen via ntg-context
2022-03-20 2:50 ` jbf via ntg-context
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=aa95fe62-eefe-f103-e292-68071c039e4a@gmail.com \
--to=ntg-context@ntg.nl \
--cc=roma83537@gmail.com \
/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).