ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: Widows, flush bottom, and word breaks
Date: Sat, 12 Feb 2005 19:33:32 +0000	[thread overview]
Message-ID: <20050212193332.1771@mail.comp.lancs.ac.uk> (raw)
In-Reply-To: <000901c51120$cfe600b0$6502a8c0@jlyond800>

Jack M. Lyon said this at Sat, 12 Feb 2005 09:35:05 -0700:

>I'm trying to learn to use ConTeXt for book publishing (wonderful program!)
>but can't seem to find answers to a couple of questions:
>
>1. How can I turn *off* protection against widows? (Last line of paragraph
>at top of page.)

This is discussed in greater detail in the new (in-progress) style
manual, normally available at:
<http://www.pragma-ade.com/general/manuals/style.pdf>
But also mirrored (pragma server down) at:
<http://context.aanhet.net/general/manuals/style.pdf>

I think what you want is:
\widowpenalty 0

>2. How can I turn on \flushbottom (LaTeX command) to space lines *inside*
>paragraphs but not *between* paragraphs?

I'm not sure. Peter Münster's email helped me understand the problem a
little more, but I think he misinterpreted your lines vs paragraphs
directive. Digging around in the source code (sigh), I do notice a
parameter that might help. Try these two in combination:

\setupinterlinespace[stretch=0.08]  % experimentation needed!
\setuptolerance[vertical,verystrict]

I'm not an expert in this area, so don't take this as the final word!
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay, Computing Dept.     atl@comp.lancs.ac.uk
 Lancaster University, InfoLab21        +44(0)1524/510.514
 Lancaster, LA1 4WA, UK             Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  parent reply	other threads:[~2005-02-12 19:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-12 10:25 server down ? Steffen Wolfrum
2005-02-12 16:21 ` Taco Hoekwater
2005-02-12 16:35   ` Widows, flush bottom, and word breaks Jack M. Lyon
2005-02-12 18:46     ` Peter Münster
2005-02-12 19:33     ` Adam Lindsay [this message]
2005-02-12 21:08       ` Peter Münster
2005-02-12 23:25         ` Adam Lindsay
2005-02-13  0:43           ` Jack M. Lyon
2005-02-13 18:11             ` Adam Lindsay
2005-02-13  8:43           ` Peter Münster
2005-02-13 14:58             ` Jack M. Lyon
2005-02-14  8:11               ` Hans Hagen
2005-02-14  8:45             ` Hans Hagen
2005-02-14 16:24               ` Peter Münster
2005-02-14 17:50                 ` Hans Hagen
2005-02-14 19:15               ` Adam Lindsay
2005-02-14 20:17                 ` Jack M. Lyon
2005-02-14 21:07                   ` Hyphenation exception list Jack M. Lyon
2005-02-14 21:40                     ` Jack M. Lyon
2005-02-15 10:32                       ` Hans Hagen
2005-02-14 22:10                     ` Vit Zyka
2005-02-14 22:53                       ` Taco Hoekwater
2005-02-14 23:26                         ` Jack M. Lyon
2005-02-15 10:35                           ` Hans Hagen
2005-02-15 10:34                         ` Hans Hagen
2005-02-15 10:31                     ` Hans Hagen
2005-02-14 22:06                   ` Widows, flush bottom, and word breaks Jack M. Lyon
2005-02-15  7:57                   ` Hans Hagen
2005-02-15  7:56                 ` Hans Hagen
2005-02-13 12:51 ` server down ? h h extern

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=20050212193332.1771@mail.comp.lancs.ac.uk \
    --to=atl@comp.lancs.ac.uk \
    --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).