ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: strange page break
Date: Thu, 06 May 2010 11:13:08 +0200	[thread overview]
Message-ID: <4BE28824.2080502@googlemail.com> (raw)
In-Reply-To: <FB3DEA34-A5A0-43F5-B784-91DB66063EF4@gmail.com>

Am 06.05.10 10:46, schrieb Otared Kavian:
> Hi Peter,
>
> I had noticed such strange page breaks before and since it was always 
> in small documents (maths problem sheets), I used an elementary 
> workaround which consists in adding a \medskip or \smallskip before 
> every \section. Actually analogous bad page breaks happen in Plain TeX 
> with \beginsection.
> Regarding the minimal example you sent, adding
> \setuphead[section][before=\smallskip]
> to the top of your document, solves the problem appearing in the first 
> section. I don't know whether this solves all other strange page 
> breaks or not.

You should at least keep the original space before the \section.

\setuphead[section][before={\allowbreak\blank[2*big]}]

The problem is indeed that ConTeXt tries to keep the header and the material
before the header together and there is no real key to control this. 
What you
can find in the core is this

% \chardef\somestructureheadbreakmethod\plusone  % 0=nothing, 
1=weighted, 2=strict, 3=vspacing
\chardef\somestructureheadbreakmethod\plusthree

but that's not what i consider to be available for the user.

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
___________________________________________________________________________________


  reply	other threads:[~2010-05-06  9:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04  5:38 Peter Münster
2010-05-05 11:42 ` Taco Hoekwater
2010-05-05 14:38   ` Peter Münster
2010-05-05 14:50     ` Taco Hoekwater
2010-05-05 14:57       ` luigi scarso
2010-05-05 15:33       ` Peter Münster
2010-05-05 15:44         ` Wolfgang Schuster
2010-05-05 16:23           ` Peter Münster
2010-05-05 16:43             ` Wolfgang Schuster
2010-05-05 17:21               ` Peter Münster
2010-05-05 17:37                 ` Wolfgang Schuster
2010-05-06  8:13                   ` Peter Münster
2010-05-06  8:46                     ` Otared Kavian
2010-05-06  9:13                       ` Wolfgang Schuster [this message]
2010-05-06  9:33                         ` Otared Kavian
2010-05-06  9:55                           ` Hans Hagen
2010-05-06 10:09                             ` Peter Münster
2010-05-06 10:18                               ` Wolfgang Schuster
2010-05-06 10:55                               ` Hans Hagen
2010-05-06 11:17                                 ` Peter Münster
2010-05-06 11:27                                   ` Hans Hagen
2010-05-06  9:44                         ` Peter Münster

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=4BE28824.2080502@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).