From: "Idris Samawi Hamid ادريس سماوي حامد" <ishamid@colostate.edu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: pagenumbering and part options [CORRECTED]
Date: Mon, 21 Nov 2011 14:33:35 -0700 [thread overview]
Message-ID: <op.v5bfh9uopw6hmh@ishamid-pc> (raw)
[please ignore other one]
Dear gang,
Ok this is embarrassing, but I can't seen to figure this one out. To solve
the current issue I need either
1. a \part, let's define it as \partsuper, that does one thing and ONLY
one thing:
\starttext
\partsuper{Super Part 1}
text <page numbers 1, 2, 3, ...., n>
\partsuper{Super Part 2}
text <page numbers 1, 2, 3, ...., n>
\stoptext
So after each partsuper, the pagenumber is reset to one. But the partsuper
is not typeset, does not generate anything in the listings, toc, etc etc.
In other words, it's completely invisible in the output, except that the
pagenumbering in reset.
One possibility: In addition to resetting the page no, \partsuper may
create document numbers of the form
\starttext
\partsuper{Super Part 1}
text <page <my-prefix>-1, <my-prefix>-2, <my-prefix>-3, ....,
<my-prefix>-n>
\partsuper{Super Part 2}
text <page numbers <my-other-prefix>-1, <my-other-prefix>-2,
<my-other-prefix>-3, ...., <my-other-prefix>-n>
\stoptext
2. The other, less sophisticated option: How do I get \setuppagenumbering
to simply just reset the current pagenumber to "1" and start from "1"
again?
Again I can do <my-prefix> for the first range of pagenumbers and
<my-other-prefix> for the second.
===================
Let me explain the big picture. I have two (rather large) structured
documents. I need to
a) compile both at the same time to manage cross-references between each;
b) have each start at page 1. \setuppagenumbering[number=1] does not seem
to work:
===========
\starttext
\dorecurse{28}{\input knuth\par }
\setuppagenumbering[state=stop]
\dorecurse{28}{\input knuth\par }
\setuppagenumbering[state=start]
\dorecurse{28}{\input knuth\par }
\setuppagenumbering[number=1]
\dorecurse{28}{\input knuth\par }
\stoptext
===========
For cross references I have defined a mirror for each document structure
element. For \chapter in Book One we use \chaptertwo in Book Two etc., so
each book has its own TOC that does not interfere with the other etc.
===================
With this in mind, I need your help, gang!
Best wishes
Idris
--
Professor Idris Samawi Hamid, Editor-in-Chief
International Journal of Shīʿī Studies
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
___________________________________________________________________________________
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
___________________________________________________________________________________
next reply other threads:[~2011-11-21 21:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 21:33 Idris Samawi Hamid ادريس سماوي حامد [this message]
2011-11-21 22:02 ` Pontus Lurcock
2011-11-21 22:09 ` Aditya Mahajan
2011-11-21 22:20 ` Idris Samawi Hamid ادريس سماوي حامد
2011-11-22 5:22 ` Wolfgang Schuster
2011-11-21 22:18 ` Idris Samawi Hamid ادريس سماوي حامد
2011-11-21 22:31 ` Idris Samawi Hamid ادريس سماوي حامد
2011-11-21 21:55 Idris Samawi Hamid ادريس سماوي حامد
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=op.v5bfh9uopw6hmh@ishamid-pc \
--to=ishamid@colostate.edu \
--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).