ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Lars Huttar <lars_huttar@sil.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: a way to implement \testcolumn in mixedcolumns
Date: Fri, 22 Nov 2013 17:37:19 -0500	[thread overview]
Message-ID: <528FDC9F.5080208@sil.org> (raw)
In-Reply-To: <528FD3AB.6080809@wxs.nl>

On 11/22/2013 4:59 PM, Hans Hagen wrote:
> On 11/20/2013 11:12 PM, Lars Huttar wrote:
>> On 11/20/2013 4:47 PM, Lars Huttar wrote:
>>> However one thing we do miss from columnsets is the control over widows
>>> & orphans in two ways: \testcolumn, and \setupcolumnsetlines.
>>> \testcolumn[n] allowed us to do a conditional column break, so when we
>>> were about to start a new subsection heading, we could prevent it being
>>> an orphan at the bottom of the column; and when starting a paragraph
>>> with a hangaround graphic framed flushright and bottom, we could
>>> similarly use \testcolumn to prevent the graphic from hanging down into
>>> the footer (which is what sometimes happened otherwise).
>>>
>>> So I'm wondering, is there some way to achieve the equivalent of
>>> \testcolumn in mixedcolumns?
>
> for the moment add \penalty10000
>

OK... where? In the same place we used to use \testcolumn?

According to http://www.tug.org/utilities/plain/cseq.html#penalty-rp,
"If <number> is 10,000 or larger, TeX will never break a line or a page
there. Also, if <number> is -10,000 or less, it will always break a line
or a page there [97 and 110]. ... Plain TeX has \break and \nobreak
macros which are defined to be: \penalty-10000 and \penalty10000."

So it sounds like you're recommending the equivalent of a \nobreak. That
wouldn't make sense in the place where we want to conditionally break
the column. So I guess you're talking about using it e.g. right after
the subsection heading, since we don't want it to break right there?

If so, that sounds like it will be helpful for preventing that
particular case.

I don't think it will work for preventing external figures from hanging
down below the bottom of the column though, will it? Because for that to
work, we'd have to prevent breaks anywhere in the flowing-around
paragraph. And I don't see a way to do that.

Thanks,
Lars

___________________________________________________________________________________
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:[~2013-11-22 22:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 21:47 Lars Huttar
2013-11-20 22:12 ` Lars Huttar
2013-11-22 21:59   ` Hans Hagen
2013-11-22 22:37     ` Lars Huttar [this message]
2013-11-23 11:49       ` Hans Hagen
2013-11-26 19:37         ` Lars Huttar
2013-11-28 18:34 ` Hans Hagen
2013-11-29 11:26   ` Lars Huttar (SIL gmail)
2013-11-29 11:46     ` Hans Hagen
2013-12-03 14:10   ` Lars Huttar
2013-12-03 21:40     ` Hans Hagen
2013-12-05 13:45       ` Lars Huttar (SIL gmail)

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=528FDC9F.5080208@sil.org \
    --to=lars_huttar@sil.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).