From: Bart Wise <bart@wiseguysweb.com>
To: ntg-context@ntg.nl
Subject: Re: How to not reset page numbers with a new part?
Date: Wed, 13 Feb 2008 05:53:57 -0700 [thread overview]
Message-ID: <200802130553.57840.bart@wiseguysweb.com> (raw)
In-Reply-To: <115224fb0802130212s6a7f6f52i9c56c28c648862c8@mail.gmail.com>
Thanks Wolfgang for spotting my error!
Bart
On Wed February 13 2008 3:12:22 am Wolfgang Schuster wrote:
> On Feb 12, 2008 11:33 PM, Bart Wise <bntgcontext@wiseguysweb.com> wrote:
> > Willi,
> >
> > I tried that and it did do what I wanted. My book has frontmatter and
> > bodymatter. The page numbering will start at 1 on the title page,
> > displayed in roman numerals. And then when the bodymatter is entered,
> > the numbering should get reset to 1. However, when I did a "way=bytext",
> > I could not reset the numbering to 1 when I was in the bodymatter
> > section.
> >
> > Any more hints?
> >
> > Just for clarity sake, here's some sample code of what I'm trying to do:
> >
> > \enablemode[doublesided]
> >
> > \setuppagenumbering[
> > location={footer,middle},
> > alternative=doublesided,
> > partnumber=no,
> > style=\em\tfx,
> > way=bytext]
> >
> > \starttext
> >
> > \startfrontmatter
> > \setuppagenumbering[conversion=romannumerals]
> >
> > \startstandardmakeup[headerstate=none]
> > Half-Title Here
> > \stopstandardmakeup
> >
> > \startstandardmakeup[doublesided=no]
> > Title Here
> > \stopstandardmakeup
> >
> > \startstandardmakeup[page=no]
> > Copyright here
> > \stopstandardmakeup
> >
> > \chapter{Preface} \dorecurse{10}{\input tufte }
> > \stopfrontmatter
> >
> > \startbodymatter
> > \setuppagenumbering[conversion=]
> > \setuppagenumbering[number=1]
>
> \setuppagenumber[number=1]
>
> > \part{Part One}
> > \chapter{first} \dorecurse{10}{\input tufte }
> > \chapter{second} \dorecurse{10}{\input davis }
> > \part{Part Two}
> > \chapter{third} \dorecurse{10}{\input zapf }
> > \chapter{fourth} \dorecurse{10}{\input bryson }
> > \stopbodymatter
> >
> > \stoptext
>
> 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://tex.aanhet.net
> archive : https://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________
>________
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2008-02-13 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 17:35 Bart Wise
2008-02-12 20:47 ` Willi Egger
2008-02-12 22:33 ` Bart Wise
2008-02-13 10:12 ` Wolfgang Schuster
2008-02-13 12:53 ` Bart Wise [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=200802130553.57840.bart@wiseguysweb.com \
--to=bart@wiseguysweb.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).