From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \setupuserpagenumber not working as expected
Date: Thu, 3 Sep 2020 06:19:22 +0200 [thread overview]
Message-ID: <408ceda6-5e88-9ac0-f5dc-8a2ef7399d83@gmail.com> (raw)
In-Reply-To: <4c941864-8f83-082c-7b10-29509bacebc5@gmail.com>
jbf schrieb am 03.09.2020 um 06:04:
> Am seeking to have frontmatter pages in roman numerals and from Chapter
> 1 onwards in arabic numerals. I have achieved something of the kind, but
> page 1 (arabic) is appearing on the last page of the frontmatter and not
> the first page of Chapter 1. I do not know why this is happening. My
> setup for page numbering is as follows (something I found somewhere -
> wiki? elsewhere? Not sure. I didn't make it up!):
>
> \definestructureconversionset[frontpart:pagenumber][][romannumerals]
> \definestructureconversionset[bodypart:pagenumber] [][numbers]
> \startsectionblockenvironment[frontpart]
> \setupuserpagenumber[numberconversion=romannumerals]
> \setuplist[chapter][pageconversionset=pagenumber]
> \setuppagenumber[number=1]
> \stopsectionblockenvironment
>
> \startsectionblockenvironment[bodypart]
> \setuppagenumber[number=1]
> \stopsectionblockenvironment
>
> The frontmatter is some 16 pages worth (ends on a verso page but that
> verso carries the arabic number 1 instead of page xvi which it should
> be, since the final paragraph on that page ends with \stopfrontmatter.
> That means Chapter 1 (immediately after \startbodymatter) is now page 2
> instead of page 1!
>
> I tried a slightly simpler version of the above which I found on
> Stackexchange:
>
> |\definestructureconversionset[frontpart:pagenumber][][romannumerals]||
> |
>
> |\startsectionblockenvironment[bodypart]|
>
> |\setcounter[userpage][1]\stopsectionblockenvironment|
>
> but it gave me the same result. Any idea how I can get the correct result?
Do you have these settings in your document?
\setupsectionblock [frontpart] [page=]
\setupsectionblock [bodypart] [page=]
When this is the case change them to
\setupsectionblock [frontpart] [page=yes]
\setupsectionblock [bodypart] [page=yes]
or add
\page
before \stopfrontmatter.
Wolfgang
___________________________________________________________________________________
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:[~2020-09-03 4:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 4:04 jbf
2020-09-03 4:19 ` Wolfgang Schuster [this message]
[not found] ` <d2d01391-cb35-1090-a28c-046b8a0ad0e8@gmail.com>
2020-09-03 14:17 ` Wolfgang Schuster
2020-09-03 8:29 ` Jan Willem Flamma
2020-09-03 22:20 ` jbf
2020-09-04 7:21 ` Jan Willem Flamma
2020-09-04 8:47 ` Wolfgang Schuster
2020-09-06 12:43 ` Jan Willem Flamma
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=408ceda6-5e88-9ac0-f5dc-8a2ef7399d83@gmail.com \
--to=wolfgang.schuster.lists@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).