The command "\setuppagenumber[state=stop]" used to stop numbering the pages, now it doesn't. Has this been changed and did I miss that change?
Hans van der Meer
More information on this. Statements:
<buffer definition for xml> \usemodule[hvdm-dvd] \starttext \xmlprocessbuffer{dvd}{xmlbuffer}{} \stoptext \endinput
in the hvdm-dvd module \setuppagenumber[state=stop] is put inside
\startxmlsetups setup-name \setuppapersize[A5][A5] \setuppagenumber[state=stop] "typesetting operations following" \stopxmlsetups In this case pagenumber not suppressed.
However with the following order of statements the pagenumber does get suppressed.
\starttext \setuppagenumber[state=stop] \xmlprocessbuffer{dvd}{xmlbuffer}{} \stoptext
In both cases the call to \setuppagenumber comes before typesetting the page. Why is the \setuppagenumber inside the xmlsetup ignored?
Hans van der Meer
On 27 Dec 2015, at 14:21, Meer, Hans van der <H.vanderMeer@uva.nlmailto:H.vanderMeer@uva.nl> wrote:
The command "\setuppagenumber[state=stop]" used to stop numbering the pages, now it doesn't. Has this been changed and did I miss that change?
Hans van der Meer
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nlmailto: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 ___________________________________________________________________________________
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?
On 27 Dec 2015, at 17:20, Meer, Hans van der <H.vanderMeer@uva.nlmailto:H.vanderMeer@uva.nl> wrote:
More information on this. Statements:
<buffer definition for xml> \usemodule[hvdm-dvd] \starttext \xmlprocessbuffer{dvd}{xmlbuffer}{} \stoptext \endinput
in the hvdm-dvd module \setuppagenumber[state=stop] is put inside
\startxmlsetups setup-name \setuppapersize[A5][A5] \setuppagenumber[state=stop] "typesetting operations following" \stopxmlsetups In this case pagenumber not suppressed.
However with the following order of statements the pagenumber does get suppressed.
\starttext \setuppagenumber[state=stop] \xmlprocessbuffer{dvd}{xmlbuffer}{} \stoptext
In both cases the call to \setuppagenumber comes before typesetting the page. Why is the \setuppagenumber inside the xmlsetup ignored?
Hans van der Meer
On 27 Dec 2015, at 14:21, Meer, Hans van der <H.vanderMeer@uva.nlmailto:H.vanderMeer@uva.nl> wrote:
The command "\setuppagenumber[state=stop]" used to stop numbering the pages, now it doesn't. Has this been changed and did I miss that change?
Hans van der Meer
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nlmailto:ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nlhttp://www.pragma-ade.nl/ / http://tex.aanhet.nethttp://tex.aanhet.net/ archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.nethttp://contextgarden.net/ ___________________________________________________________________________________
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nlmailto: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 ___________________________________________________________________________________
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.
Wolfgang
On 27 Dec 2015, at 21:57, Wolfgang Schuster <schuster.wolfgang@gmail.commailto:schuster.wolfgang@gmail.com> wrote:
Meer, Hans van dermailto: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 already tried in vain \global\settuppagenumber
Hans van der Meer
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
-
Meer, Hans van der -
Wolfgang Schuster