From: Thomas A.Schmitz <thomas.schmitz@uni-bonn.de>
Subject: Re: Pagebreaks
Date: Sun, 28 Sep 2003 22:22:23 +0200 [thread overview]
Message-ID: <784E3AF4-F1F1-11D7-9687-00039318D414@uni-bonn.de> (raw)
Kudos to Patrick for pointing out what was wrong with my file--he
helped me immensely, and I'm very grateful to him. The solution is: in
addition to \clubpenalty and \widowpenalty, there is also
\brokenpenalty, which enforces the good old typographical rule that no
page should be broken after a hyphenated word. When I set it to 0, all
my pages had exactly the same number of lines. Thanks to Patrick, and
may others find it useful!
Thomas
next reply other threads:[~2003-09-28 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 20:22 Thomas A.Schmitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-27 7:48 Pagebreaks Thomas A.Schmitz
2003-09-27 18:20 ` Pagebreaks Patrick Gundlach
2003-09-26 8:42 Pagebreaks Thomas A.Schmitz
2003-09-26 16:15 ` Pagebreaks Hans Hagen
2003-09-26 16:34 ` Pagebreaks Thomas A.Schmitz
2003-09-27 6:34 ` Pagebreaks Patrick Gundlach
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=784E3AF4-F1F1-11D7-9687-00039318D414@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).