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 17:43:38 -0600	[thread overview]
Message-ID: <871vbqbu51.fsf@notengoamigos.org> (raw)
In-Reply-To: <4C2923DB.6020002@googlemail.com> (Wolfgang Schuster's message of "Tue, 29 Jun 2010 00:36:11 +0200")

On Mon, Jun 28 2010, Wolfgang Schuster wrote:

> Am 29.06.10 00:17, schrieb Jason Earl:
>> I am having a bit of a problem with some documents that I am trying to
>> lay out in Context.  The idea is that section contents are formatted in
>> two columns, but in some cases Context leaves a huge space between the
>> section header and the content.
>>
>> I have included a sample context file (test.tex) and the output I get
>> from running:
>>
>> context test.tex
>>
>> using the newest version of context minimals.  I expect "1.2.1 Test
>> SubSection 1" and "1.2.2 Test SubSection 2" to be on the same page as
>> "Problem Header," but, as you can see, they aren't.
>>
>> I appreciate any help in sorting this out.
>>
>> I'm new to Context, and not particularly experienced in typesetting
>> either, so if you have any other advice I would appreciate that too :).
>>    
>
> You can force a page break before the second section with
>
> \page
> \section{Problem Header}
>
> to keep the header and the columns together.
>
> Wolfgang

OK, that's embarrassing.  I tried using \page[no] after the \section
header, but it did not occur to me to put a manual break before the
header.  That worked perfectly.

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.

Thanks for the help,

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-28 23:43 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 [this message]
2010-06-29  0:09     ` Aditya Mahajan
2010-06-29  2:04       ` Jason Earl

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=871vbqbu51.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).