This is the mail archive of the
mailing list .
Jadetex - Page numbers: Roman, Arabic - Confused
- To: docbook-apps at lists dot oasis-open dot org
- Subject: DOCBOOK-APPS: Jadetex - Page numbers: Roman, Arabic - Confused
- From: Ian Castle <bb+lists dot docbook-apps at looksystems dot co dot uk>
- Date: Fri, 20 Apr 2001 13:11:03 +0100
Simple Problem: I want Verso/Recto title page to have no numbers,
Contents, Preface to have lower case roman numeral page numbering
Chapters through to the end of the book to have arabic numerals starting
1,2,3..... The document is to be single sided (two sided is another
I'm confused because other people on the list (e.g
http://sources.redhat.com/ml/docbook-apps/2001-q1/msg00434.html) seem to
this working, but I don't.
- Docbook DTD 4.1 (and 3.1).
- Style sheets unadulterated DSSSL 1.61
- Open Jade 1.3 + Patches for enhanced table support etc (to go with
- JadeTex 3.4, 3.6
- TeTeX 1.0.7 + patches that come with Redhat 7.0 + hyperref 6.71a (as
jadetex 3.x requires it) + fancyhdr 2.0 2000/10/11.
What I get:
I observe that I have:
(define ($page-number-format$ #!optional (gi (gi)))
((equal? (normalize gi) (normalize "toc")) "i")
((equal? (normalize gi) (normalize "lot")) "i")
((equal? (normalize gi) (normalize "preface")) "i")
in my style sheets and after running jade I can see lots of
in the resulting .tex file.
If I change the style sheet, to say, I or 1 or whatever then I see
corresponding changes in the output, so I conclude that jade and the
stylesheets are doing the correct thing.
Looking at jadetex.dtx, the only place where \PageNumberFormat is used
to me* [I am no TeXpert or TeXnician!] in the definition of the \endSpS
"macro". I guess that this macro is run whenever a DSSSL
"simple-page-sequence" is terminated. The relevant part seems to be:
Which, and I don't profess to understand it at all, I assume is saying
"at the end of the simple-page-sequence if we are restarting numbering,
globally (i.e. outside of the scope of the \EndSpS macro) set the page
This seems reasonable (given the proviso that the first s-p-s will be
rendered in arabic as PageNumberFormat is only checked at the end of the
s-p-s - which is OK as my first s-p-s is the title page where I don't
actually want any numbers...)
However - this just seems to be attempting to set the format. It doesn't
actually cause the page number to be printed.
In the .tex file produced by jade I notice that there is one
\insertPageNumber for every page number to be produced...
... but... (and this is where my confusion starts)... \insertPageNumber
defined in jadetex.dtx as
Note the "\arabic" which seems to be saying (and empirical evidence
that it is) that it will ALWAYS use an arabic format regardless of the
anything set anywhere else.
If I put the following definition in my jadetex.cfg
Then I get what I want. Which is nice - but not necessarily very robust.
Especially the bit that resets the page number to 1 - this fails
I use the dsssl style sheet option %page-number-restart%).
But I can't see how it can possibly work if you don't do something like
Of course, if I do have a preface with roman numerals on the page, then
the table of contents it is rendered in arabic numerals. I can't even
to conceive of how this could be remedied as the page number format
seem to be some "state" that is associated with the page element - just
thing that gets worked out as the page number is actually rendered....
I had wondered if it was something to do with "fancyhdr" which I don't
understand. I notice in jadetex 3.6 that it now requires
fancyhdr[2000/10/10]. But searching through CTAN and anywhere else only
reveals a fancyhdr.sty that does not contain a "\ProvidesFile" or
"\ProvidesPackage" statement anywhere - just mentions 2.0 and 11/10/2000
So where am I going wrong?
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: email@example.com