From: Guy Worthington <guyw@multiline.com.au>
Subject: Re: Lost in the murky detail of designing a page layout
Date: 09 Feb 2003 14:36:05 +0800 [thread overview]
Message-ID: <uisvuc65m.fsf@multiline.com.au> (raw)
In-Reply-To: <878ywttyrq.fsf@gundla.ch>
Hello again Patrick,
The reason I've taken so long to reply, is that I've been trying to
understand TeX's line-breaking mechanism. Your perceptive question:
> Why is there a difference between knuth.tex and tufte.tex in the
> example (try \input tufte instead of \input knuth).
In the example below
%-- tryISOLayout.ctx ----------------------------------------
%output=pdf
\setuppapersize[A4][A4]
\setupencoding[default=texnansi]
\setupbodyfont[cmr,14.4pt]
\def\GoldenRatio{1.61803}
\setbox0\hbox{\dorecurse{26}{\character\recurselevel}}
\setuplayout[width=2.5\wd0,
header=\lineheight,
footer=\lineheight,
height=\GoldenRatio\makeupwidth,
headerdistance=\dimexpr(
(\makeupheight-37\lineheight-\headerheight-\footerheight) /2),
footerdistance=\headerdistance,
backspace=\dimexpr(\makeupwidth/7),
topspace=\dimexpr(\makeupwidth/7)]
\showframe
\starttext
\startlinenumbering
\dorecurse{5}{\input tufte}
\stoplinenumbering
\stoptext
%-- end tryISOLayout.ctx ------------------------------------
I think is due to TeX trying very hard not to generate a widow line.
Even after fiddling around with \looseness, I couldn't force TeX to
add the 37th line. I've a feeling that if you come across a
pathological case like the above, you really have to follow Knuth's
advice and rewrite the paragraph.
next prev parent reply other threads:[~2003-02-09 6:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 8:55 Guy Worthington
2003-02-04 9:44 ` Patrick Gundlach
2003-02-05 8:07 ` Guy Worthington
2003-02-05 9:24 ` Hans Hagen
2003-02-06 8:48 ` Guy Worthington
2003-02-06 11:49 ` Patrick Gundlach
2003-02-07 8:22 ` Hans Hagen
2003-02-09 6:36 ` Guy Worthington [this message]
2003-02-09 18:31 ` 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=uisvuc65m.fsf@multiline.com.au \
--to=guyw@multiline.com.au \
--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).