From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \setuphead problem
Date: Sat, 3 Mar 2012 15:58:53 +0100 [thread overview]
Message-ID: <BA567452-DF81-4985-AEBD-EFF653925DAC@googlemail.com> (raw)
In-Reply-To: <CAFMOkGWxgsJ7SvHv+vZg+Dbn7Xbve9aotDG0UvyAdNwxaKicfw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1090 bytes --]
Am 03.03.2012 um 14:43 schrieb Alan Bowen:
> Excellent, Wolfgang. You are right. Many thanks. But if I may impose just a little longer on your patience, let me explain my problem further.
>
> In my example, that \page[makeup] to be removed stood for a key element in the sequence
> \page[makeup]
> \stoptext
> \stopcomponent
> that typically closes a component in the prd file that I use to produce volumes of a journal.
Why do you use \stoptext before \stopcomponent?
> Without \page[makeup], when I run my prd file, the page number of a component is appears on the last page of the preceding component. If I keep the \page[makeup], each component is followed by a blank page (with header) that precedes the title page of the new component.
>
> In short my example replicated what I was seeing but fixing the example does not fix the original problem. Is there a canonical way to close components in MKIV that I have missed? (This env/prd setup does work in MKII—I have 8 volumes to show for it.)
Can you make a example or send me the files offlist.
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 1610 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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-03-03 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 17:37 Alan Bowen
2012-03-01 23:24 ` Wolfgang Schuster
2012-03-02 13:11 ` Alan Bowen
2012-03-02 15:30 ` Wolfgang Schuster
2012-03-02 16:35 ` Alan Bowen
2012-03-03 8:37 ` Wolfgang Schuster
2012-03-03 13:43 ` Alan Bowen
2012-03-03 14:58 ` Wolfgang Schuster [this message]
2012-03-03 17:53 ` Alan Bowen
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=BA567452-DF81-4985-AEBD-EFF653925DAC@googlemail.com \
--to=schuster.wolfgang@googlemail.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).