From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/93191 Path: news.gmane.org!not-for-mail From: "Meer, Hans van der" Newsgroups: gmane.comp.tex.context Subject: Re: how to stop pagenumbering Date: Sun, 27 Dec 2015 21:25:01 +0000 Message-ID: <90FE051A-3B6B-426C-8CAD-D996C44705AE@uva.nl> References: <4B014CFD-220A-4C61-9E9E-1051D4A2B2B5@uva.nl> <0DDF9C53-6588-4A48-B692-CECD084BECD9@uva.nl> <568050BD.5070309@gmail.com> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8041556770665364272==" X-Trace: ger.gmane.org 1451251549 30167 80.91.229.3 (27 Dec 2015 21:25:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 27 Dec 2015 21:25:49 +0000 (UTC) To: NTG ConTeXt Original-X-From: ntg-context-bounces@ntg.nl Sun Dec 27 22:25:37 2015 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aDIoo-0004L3-Pk for gctc-ntg-context-518@m.gmane.org; Sun, 27 Dec 2015 22:25:34 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id A9D7B5AB9; Sun, 27 Dec 2015 22:25:15 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yi5D14OAdZlG; Sun, 27 Dec 2015 22:25:13 +0100 (CET) Original-Received: from zapf.ntg.nl (localhost [IPv6:::1]) by zapf.ntg.nl (Postfix) with ESMTP id 8918A5AB6; Sun, 27 Dec 2015 22:25:13 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id EF4B45AB2 for ; Sun, 27 Dec 2015 22:25:12 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AFDrGXqfH9Xy for ; Sun, 27 Dec 2015 22:25:12 +0100 (CET) Original-Received: from HUB01.uva.nl (hub01.uva.nl [146.50.108.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by zapf.ntg.nl (Postfix) with ESMTPS id 82E3F5AAF for ; Sun, 27 Dec 2015 22:25:02 +0100 (CET) Original-Received: from MBX02.uva.nl ([169.254.2.34]) by HUB01.uva.nl ([2002:9232:6737::9232:6737]) with mapi id 14.03.0266.001; Sun, 27 Dec 2015 22:25:02 +0100 Thread-Topic: [NTG-context] how to stop pagenumbering Thread-Index: AQHRQKmBg7HDhyYo6kuZ8OlaidST/p7e8s2AgABKtQCAAALRgIAAB6yA In-Reply-To: <568050BD.5070309@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [84.106.134.200] x-endpointsecurity-0xde81-ev: v:6.2.7.696, d:out, a:y, w:t, t:15, sv:1451238318, ts:1451251502 X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.16 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntg-context-bounces@ntg.nl Original-Sender: "ntg-context" Xref: news.gmane.org gmane.comp.tex.context:93191 Archived-At: --===============8041556770665364272== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_90FE051A3B6B426C8CADD996C44705AEuvanl_" --_000_90FE051A3B6B426C8CADD996C44705AEuvanl_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On 27 Dec 2015, at 21:57, Wolfgang Schuster > wrote: Meer, Hans van der 27. Dezember 2015 um 21:47 One more observation on the strangeness of \setuppagenumber. Putting \setuppagenumber[number=3D4] before the call to \xmlprocessbuffer a= nd putting \setuppagenumber[state=3Dstop,number=3D8] inside the \startxmlse= tups does make the pagenumber having the value 8. This proves two things: (1) the \setuppagenumber in the \startxmlsetups is processed before the pag= enumber is fixed and typeset (2) the [state=3Dstop] in the \startxmlsetups is wrongfully ignored, wherea= s at the same time [number=3D8] does get honored. Imho this demonstrates there is an error in the processing of \setuppagenum= ber when located inside the \startxmlsetups. An error that does not occur w= hen 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 --_000_90FE051A3B6B426C8CADD996C44705AEuvanl_ Content-Type: text/html; charset="iso-8859-1" Content-ID: <51A6883414D83F49BADA5D9D3304522F@uva.nl> Content-Transfer-Encoding: quoted-printable
On 27 Dec 2015, at 21:57, Wolfgang Schuster <schuster.wolfgang@gmail.com<= /a>> wrote:

Meer, Hans van der
27. Dezember 2015 um 21:47
One more observation on the strangeness of \setuppagenumber.

Putting \setuppagenumber[number=3D4] before the call to \xmlprocessbuffer and putting<= span class=3D"" style=3D"font-family: Courier;"> \setuppagenumber[state=3Dstop,number=3D8= ] inside the \startxmlsetups does make the pagenumber having the value 8. Th= is proves two things:

(1) the \setuppagenumber = in the \startx= mlsetups is processed before = the pagenumber is fixed and typeset

(2) the [state=3Dstop] in= the \startxml= setups is wrongfully ignored,= whereas at the same time [number=3D8] does get honored.

Imho this demonstrates th= ere is an error in the processing of \setuppagenumber when located inside t= he \startxmlse= tups. An error that does not occur when called at the \starttext document-level before th= e \xmlprocessb= uffer. =
Could it be a matter of l= ocality?

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 betwe= en \begingroup .. \endgroup.
That would explain the behaviour.
The remedy then could be a more glob= al execution of \setuppagenumber.
I already tried in vain \global\sett= uppagenumber
Hans van der Meer



--_000_90FE051A3B6B426C8CADD996C44705AEuvanl_-- --===============8041556770665364272== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv IGh0dHA6Ly90ZXguYWFuaGV0Lm5ldAphcmNoaXZlICA6IGh0dHA6Ly9mb3VuZHJ5LnN1cGVsZWMu ZnIvcHJvamVjdHMvY29udGV4dHJldi8Kd2lraSAgICAgOiBodHRwOi8vY29udGV4dGdhcmRlbi5u ZXQKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX18= --===============8041556770665364272==--