ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: jbf via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen via ntg-context <ntg-context@ntg.nl>
Cc: jbf <roma83537@gmail.com>
Subject: Re: how to change metadata halfway through document
Date: Mon, 30 Jan 2023 20:20:40 +1100	[thread overview]
Message-ID: <18ae75a6-c5da-5fdb-7b82-d0b6553e5a9e@gmail.com> (raw)
In-Reply-To: <dae4ca97-9f48-ae36-13de-ae3b3751c6ca@freedom.nl>

Indeed, that works. Thank you.

Julian

On 30/1/23 20:14, Hans Hagen via ntg-context wrote:
> On 1/30/2023 1:14 AM, jbf via ntg-context wrote:
>> Am trying to understand how best to change the title metadata in 
>> headertext halfway through a document that has two parts: 
>> Constitutions and Regulations.
>>
>> My first attempt (did not work)
>>
>> \startsetups[headertext]
>>
>> \startdocument
>>
>> [metadata:title={Regulations}]
>>
>> \stopsetups
>>
>> \setupheadertexts
>>
>> [ ] [{\getmarking[chapter]\hskip1em \pagenumber}]
>>
>> [{\pagenumber \hskip1em \setup{headertext}}] [ ]
>>
>> My second attempt (quite crass, but it works!!) was to create a 
>> second \startdocument within the main \startdocument (obviously 
>> closing it towards the end but before the main \stopdocument), this 
>> time with [metadata:title={Regulations}] instead of the original 
>> [metadata:title={Constitutions}]. However, I have a strong feeling 
>> this is not a very elegant solution!
> you can try \setupdocument but i didn't test that
>
>
> -----------------------------------------------------------------
>                                           Hans Hagen | PRAGMA ADE
>               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------
>
> ___________________________________________________________________________________ 
>
> If your question is of interest to others as well, please add an entry 
> to the Wiki!
>
> maillist : ntg-context@ntg.nl / 
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki     : https://contextgarden.net
> ___________________________________________________________________________________ 
>
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2023-01-30  9:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30  0:14 jbf via ntg-context
2023-01-30  9:14 ` Hans Hagen via ntg-context
2023-01-30  9:20   ` jbf via ntg-context [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=18ae75a6-c5da-5fdb-7b82-d0b6553e5a9e@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).