From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bug in latest beta?
Date: Sun, 31 May 2015 13:56:40 +0200 [thread overview]
Message-ID: <556AF6F8.5020704@gmx.es> (raw)
In-Reply-To: <55674C14.4040508@wxs.nl>
On 05/28/2015 07:10 PM, Hans Hagen wrote:
> On 5/27/2015 10:38 PM, Pablo Rodriguez wrote:
>> [...]
>> Compiling it with beta from 2015.03.25 22:13, page break is fine.
>>
>> But with latest beta from 2015.05.24 12:42 (or even with beta from
>> 2015.05.15 11:42 includes a wrong page break. The setups for widow and
>> orphan lines move the two last lines to the next page.
>>
>> Could anyone confirm this bug?
>
> i wonder if it's a bug or just tex's decision ... you can use
>
> \showmakeup[penalty]
>
> and see what penalties get injected
>
> are the linebreaks identical, i.e. same hyphenation?
Many thanks for your reply, Hans.
Hyphenation is the same in both documents.
> btw, brokenpenalty 1 gives a different result
Page break is wrong when any of the three values (brokenpenalty,
widowpenalty or clubpenalty) is 0 or above 9999.
I replacing \subsection with \section gives the right page break:
\showframe\showgrid
\setuplayout[setups=*lessstrict]
\startsetups[*lessstrict]
\setup[reset]
\widowpenalty=10000
\clubpenalty=10000
\brokenpenalty=0
\stopsetups
\setupbodyfont[pagella, 12.6pt]
\starttext
\chapter{Quotes}
\section{Zapf}
\dorecurse{4}{\input zapf\par}
\section{Knuth}
\input knuth
\stoptext
Why does \subsection cause a different page break than \section?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2015-05-31 11:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 20:38 Pablo Rodriguez
2015-05-28 14:59 ` Otared Kavian
2015-05-31 11:34 ` Pablo Rodriguez
2015-05-28 17:10 ` Hans Hagen
2015-05-31 11:56 ` Pablo Rodriguez [this message]
2015-05-31 22:16 ` Hans Hagen
2015-06-01 6:45 ` Otared Kavian
2015-06-01 7:28 ` Pablo Rodriguez
2015-06-01 7:41 ` Otared Kavian
-- strict thread matches above, loose matches on Subject: below --
2017-11-01 13:18 Pablo Rodriguez
2017-11-01 15:50 ` Pablo Rodriguez
2016-09-05 8:39 Akira Kakuto
2016-09-05 14:33 ` Pablo Rodriguez
2016-09-05 14:44 ` luigi scarso
2016-09-05 15:32 ` Pablo Rodriguez
2016-09-05 5:59 Pablo Rodriguez
2016-09-05 6:36 ` josephcanedo
2016-09-05 15:10 ` Pablo Rodriguez
2016-09-06 4:43 ` Pablo Rodriguez
2015-05-14 20:46 Pablo Rodriguez
2015-05-15 5:07 ` Pablo Rodriguez
2014-12-10 18:51 Pablo Rodriguez
2014-12-10 19:14 ` Hans Hagen
2014-12-10 19:59 ` Pablo Rodriguez
2014-05-26 5:47 Pablo Rodriguez
2014-05-26 8:24 ` Hans Hagen
2014-05-26 15:44 ` Pablo Rodriguez
2014-03-18 17:30 Pablo Rodriguez
2014-03-18 17:39 ` Wolfgang Schuster
2014-03-18 17:52 ` Pablo Rodriguez
2008-11-10 9:55 Chen Shen
2008-11-10 11:59 ` Wolfgang Schuster
2008-11-10 12:37 ` Chen Shen
2008-11-10 15:25 ` Hans Hagen
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=556AF6F8.5020704@gmx.es \
--to=oinos@gmx.es \
--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).