From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bug in widows and orphans prevention?
Date: Tue, 23 Aug 2016 20:46:34 +0200 [thread overview]
Message-ID: <57BC9A0A.9050909@gmail.com> (raw)
In-Reply-To: <f001516d-e0e1-20d4-9e9e-381a21c30ece@gmx.es>
[-- Attachment #1.1: Type: text/plain, Size: 838 bytes --]
> Pablo Rodriguez <mailto:oinos@gmx.es>
> 23. August 2016 um 20:35
> Dear list,
>
> I have the following sample:
>
> \showframe\showgrid
> \startsetups[orphanwidow]
> \setup[reset]
> \widowpenalty=10000
> \clubpenalty=10000
> \brokenpenalty=1
> \stopsetups
> \setuplayout[setups={orphanwidow}]
> \setupbodyfont[12.5pt]
> %~ \setupbodyfont[pagella]
> \starttext
> \dorecurse{10}{\input zapf\par}
> \stoptext
>
> With both typefaces (Latin Modern at 12.5pt and TeX Gyre Pagella at
> 12pt), I get an orphan line on the second page.
>
> Have I hit a bug or am I missing something?
You can use the \setpenalties command which gives you more options.
\startsetups[orphanwidow]
\directsetup{*reset}
\setpenalties \widowpenalties{1}{10000}
\setpenalties \clubpenalties {1}{10000}
\brokenpenalty\plusone
\stopsetups
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 1951 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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:[~2016-08-23 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 18:35 Pablo Rodriguez
2016-08-23 18:46 ` Wolfgang Schuster [this message]
2016-08-23 20:42 ` Pablo Rodriguez
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=57BC9A0A.9050909@gmail.com \
--to=schuster.wolfgang@gmail.com \
--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).