ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jason Earl <jearl@notengoamigos.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with large space after section header
Date: Mon, 28 Jun 2010 20:04:54 -0600	[thread overview]
Message-ID: <87wrtioapl.fsf@notengoamigos.org> (raw)
In-Reply-To: <alpine.LNX.2.01.1006282007220.8852@ybpnyubfg.ybpnyqbznva>

On Mon, Jun 28 2010, Aditya Mahajan wrote:

> On Mon, 28 Jun 2010, Jason Earl wrote:
>
>> In my defense, part of the reason that I did not think of putting in a
>> manual page break before the section is that my real context documents
>> are generated from a script, and I did not want to have to process the
>> output by hand to solve these sorts of problems.  I was hoping for some
>> sort of magic that I could put after every section heading that would
>> make Context try harder to keep the content close to the header.
>>
>> However, while I don't pretend to be an expert at typesetting I do
>> understand that automating this stuff is hard, and sometimes there is no
>> real way to fix issues like this.  If I have to do a little hand
>> massaging of the output that's acceptable.
>
> In an automated setup, you can try
>
> \setuphead[section][before={\blank\testpage[4]}]
>
> \testpage[n] tests if there is enough space to put n lines in the
> current page. If not, it insearts a pagebreak. Play around with n to
> see what gives best result.

Thank you so much.  That looks like it is going to solve the most
problematic spaces without having to manually insert page breaks.  In
fact, to my untutored eye even without playing with the numbers it looks
perfect.  That was precisely the magic I needed, and it even came with
an explanation that should help me solve similar problems myself in the
future.

Thanks to Wolfgang for responding as well.  I am sorry I was not more
clear with my original report.

Thanks again,
Jason
___________________________________________________________________________________
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-06-29  2:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28 22:17 Jason Earl
2010-06-28 22:36 ` Wolfgang Schuster
2010-06-28 23:43   ` Jason Earl
2010-06-29  0:09     ` Aditya Mahajan
2010-06-29  2:04       ` Jason Earl [this message]

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=87wrtioapl.fsf@notengoamigos.org \
    --to=jearl@notengoamigos.org \
    --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).