From: "Jack M. Lyon" <jack.lyon@comcast.net>
Subject: RE: Widows, flush bottom, and word breaks
Date: Mon, 14 Feb 2005 13:17:43 -0700 [thread overview]
Message-ID: <000a01c512d2$45e38d20$cd050a0a@jlyond800> (raw)
In-Reply-To: <20050214191500.9793@mail.comp.lancs.ac.uk>
With lots of help from Adam and some tinkering on my own, here's what seems
to be working best for me:
\setupinterlinespace[stretch=0.08]
\setuptolerance[vertical,stretch]
\setupalign[height]
This produces a flush bottom with very even interline and interparagraph
spacing, all vertically justified. Nice!
I'm very grateful for the help from one and all.
Best wishes,
Jack M. Lyon
___________________________________________________
The EDITORIUM
Microsoft Word Add-Ins for Publishing Professionals
http://www.editorium.com
___________________________________________________
> -----Original Message-----
> From: ntg-context-bounces@ntg.nl
> [mailto:ntg-context-bounces@ntg.nl] On Behalf Of Adam Lindsay
> Sent: Monday, February 14, 2005 12:15 PM
> To: mailing list for ConTeXt users
> Subject: Re: [NTG-context] Widows, flush bottom, and word breaks
>
>
> Hans Hagen said this at Mon, 14 Feb 2005 09:45:15 +0100:
>
> >\setuplayout[height=10cm] \setuptolerance[vertical,verytolerant]
> >
> >\setupalign[line]
>
> Okay, that's the command I *should* have found, right? :)
> Sigh, and it's
> right there in the manual.
> What I found today was \alignbottom (and its relatives), which I now
> presume is ancient and deprecated?
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> 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
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
next prev parent reply other threads:[~2005-02-14 20:17 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
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 [this message]
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='000a01c512d2$45e38d20$cd050a0a@jlyond800' \
--to=jack.lyon@comcast.net \
--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).