From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: how to stop pagenumbering
Date: Sun, 27 Dec 2015 22:32:07 +0100 [thread overview]
Message-ID: <568058D7.1000805@gmail.com> (raw)
In-Reply-To: <90FE051A-3B6B-426C-8CAD-D996C44705AE@uva.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1666 bytes --]
> Meer, Hans van der <mailto:H.vanderMeer@uva.nl>
> 27. Dezember 2015 um 22:25
>
>> On 27 Dec 2015, at 21:57, Wolfgang Schuster
>> <schuster.wolfgang@gmail.com <mailto:schuster.wolfgang@gmail.com>>
>> wrote:
>
>> Meer, Hans van der <mailto:H.vanderMeer@uva.nl>
>> 27. Dezember 2015 um 21:47
>>> One more observation on the strangeness of \setuppagenumber.
>>>
>>> Putting \setuppagenumber[number=4] before the call to
>>> \xmlprocessbuffer and putting\setuppagenumber[state=stop,number=8]
>>> inside the \startxmlsetups does make the pagenumber having the value
>>> 8. This proves two things:
>>>
>>> (1) the \setuppagenumber in the \startxmlsetups is processed before
>>> the pagenumber is fixed and typeset
>>>
>>> (2) the [state=stop] in the \startxmlsetups is wrongfully ignored,
>>> whereas at the same time [number=8] does get honored.
>>>
>>> Imho this demonstrates there is an error in the processing of
>>> \setuppagenumber when located inside the \startxmlsetups. An error
>>> that does not occur when called at the \starttext document-level
>>> before the \xmlprocessbuffer.
>>> Could it be a matter of locality?
>
>> You have to provide a *working* minimal example.
>
> Not so simple, alas.
> But I will be greatly helped if you can ascertain that
>
> \startxmlsetups
> code within
> \stopxmlsetups
>
> is code executed locally as if between \begingroup .. \endgroup.
> That would explain the behaviour.
> The remedy then could be a more global execution of \setuppagenumber.
I have to disappoint you but the content of the setups environment isn't
grouped.
> I already tried in vain \global\settuppagenumber
This doesn't work here.
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 6094 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2015-12-27 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-27 13:21 Meer, Hans van der
2015-12-27 16:20 ` Meer, Hans van der
2015-12-27 20:47 ` Meer, Hans van der
2015-12-27 20:57 ` Wolfgang Schuster
2015-12-27 21:25 ` Meer, Hans van der
2015-12-27 21:32 ` Wolfgang Schuster [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=568058D7.1000805@gmail.com \
--to=schuster.wolfgang@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).