ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Page number woes
Date: Tue, 15 Mar 2016 11:22:12 +0100	[thread overview]
Message-ID: <56E7E254.1080907@gmail.com> (raw)
In-Reply-To: <CAGbDsP1nHGYra1omYSZ-xmb3Fmzbd2hgM1_bV1cD13a4xwJrVg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1939 bytes --]

> Mari Voipio <mailto:mari.voipio@iki.fi>
> 14. März 2016 um 15:43
> Greetings all!
>
> I have a book setup that worked perfectly as long as the inside cover
> was only one page long. But then we added information to the inside
> cover and had to split the information on two pages. The so called
> inside cover works fine, the TOC works fine, but the main text part
> (starting with Intro) begins now on page 2 when it should be on page
> 1. And this happens even when the TOC is two pages long, which is a
> bit weird (I would assume that if it counts TOC into page numbers,
> two-page TOC would mean that Intro starts on page 3, but nope, it
> still starts on page 2).
>
> The minimal sample attached to this message is really ugly as it
> doesn't contain any of the environment files, but the problem is
> visible here just as well as in the real thing - if I make the second
> page of the inside cover disappear, Intro starts on page 1 as it
> should. If the so called inside cover is two pages long, Intro starts
> on page 2. (The file to be compiled is prd-pr43-general_test.tex, the
> others are component files.)
>
> It is quite possible the TOC file is the culprit and it has been pure
> luck that everything has worked until now... I don't understand the
> page mechanism in ConTeXt well enough to see where the problem is.
>
> I noticed that my ConTeXt version is pretty old: "ConTeXt ver:
> 2015.02.03 23:55 MKIV beta" (hmm... I didn't update at ConTeXt meeting
> as I usually do, stupid me.)
> I'd rather not update just now (production in sensitive phase), but if
> you think the problem will go away with an update, I'll do it.
Move your intro text after the \startfrontmatter command everything before
it doesn’t belong to any sectionblock.

You can also omit \startext and \stoptext commands when you \startcomponent
etc. because they already do the work of \starttext.

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 3026 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2016-03-15 10:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 14:43 Mari Voipio
2016-03-15 10:22 ` Wolfgang Schuster [this message]
2016-03-15 12:08 ` Pablo Rodriguez
2019-09-02 11:07 Mari Voipio
2019-09-03 16:03 ` Wolfgang Schuster
2019-09-05  9:30   ` Mari Voipio

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=56E7E254.1080907@gmail.com \
    --to=schuster.wolfgang@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).