ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan Bowen <bowenalan03@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \setuphead problem
Date: Fri, 2 Mar 2012 08:11:09 -0500	[thread overview]
Message-ID: <CAFMOkGVmek3BWqPhbNOc33-4TAevsoettFgtZU8Aqhr_aWGx-A@mail.gmail.com> (raw)
In-Reply-To: <8787B4DC-A154-43FA-81CA-01636FBC5A94@googlemail.com>


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

Wolfgang—

I checked and the example fails in both MKII andf MKIV. My apologies for
carelessness. The problem arose originally in the pagination/headers for
components in a component/product structure that I am tying to set using
MKIV. In trying to devise a simple example by adapting the code in my MKII
environment file (which runs without any problems), I was so focused on
getting the code to run in MKIV that I neglected to run that code *by itself
* through MKII.

So, the question remains: What should I include or change in this example
to keep the header associated with a given title off the preceding page in
MKIV? Or is this expected behavior and my example, then, a poor one for my
purposes?

Alan

On Thu, Mar 1, 2012 at 6:24 PM, Wolfgang Schuster <
schuster.wolfgang@googlemail.com> wrote:

>
> Am 01.03.2012 um 18:37 schrieb Alan Bowen:
>
> > The following code works in MKII; but in MKIV, I get the header text on
> the page before the page with the title. How can I fix this?
>
> Can you show the output of mkii and mkiv because i can’t see a difference
> between both.
>
> 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  : http://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
>
> ___________________________________________________________________________________
>

[-- Attachment #1.2: Type: text/html, Size: 2362 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:[~2012-03-02 13:11 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 [this message]
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
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=CAFMOkGVmek3BWqPhbNOc33-4TAevsoettFgtZU8Aqhr_aWGx-A@mail.gmail.com \
    --to=bowenalan03@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).