ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Stefan Müller" <warrence.stm@gmx.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: d_jan <d_jan@ymail.com>
Subject: Re: [***SPAM***] Widows: penalty without efffect (ConTeXt iv)
Date: Thu, 09 Aug 2012 14:25:00 +0200	[thread overview]
Message-ID: <5023AC1C.7070401@gmx.de> (raw)
In-Reply-To: <50238498.5010408@ymail.com>

Hi,

did you see [1]? You have to do something like

\starttext
\clubpenalty=10000
\widowpenalty=10000

My text that should not contain any widow or orphan lines.
\stoptext

If that does not work for you, please provide a minimal example.

HTH,
Stefan


[1] 
http://archive.contextgarden.net/message/20111211.162442.4f689e7b.en.html

On 09.08.2012 11:36, d_jan wrote:
> Dear List,
>
> I ran into trouble with the widow/orphan-control in context.
> I searched the mailinglist, and saw that there were some other threads
> on the topic bevore, but as far as I am concerned what was suggested
> there did not work for me when I tried it.
>
> I run context iv using the version which comes with TexLive 2011.
>
> First trail was to include \widowpenalty=9000 and \clubpenalty=9000 at
> the start of the document, before \starttext (cause I do my setups, and
> definitions there)
> As this did not work I tried to put them after \starttext. As well I
> lowered \brokenpenalty. But both approaches, which were suggested in
> previous Posts on the ntg-context list failed to show an effect in my case.
>
> Is there anything I could do to prevent the widow lines?
>
> PS.: As I may be doing any noobish errors, here an overview of the
> documents structure and the placement of the penalty-commands
> _________________________________
>
> \widowpenalty=9000
> \clubpenalty=9000
>
> \definepapersize[janssize][width=190mm, height=245mm]
>
> \setuppapersize[janssize][A4] %we can use something like [A5][A4], which
> is a a5 Page sized Document printed on a A4 sheet
>
>
> \setuplayout[grid=yes, marking=on, location=middle, backspace=30mm,
> width=110mm]%former: location=doublesided
>
>
> \starttext
>
> \startstandardmakeup
> \stopstandardmakeup
>
> \startfrontmatter
> %TOC...
> \stopfrontmatter
>
> \startbodymatter %the main stuff goes here
> % Loads of text
> \stopbodymatter
>
> \startappendices %appendices go here
> \stopappendices
>
> \stoptext
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2012-08-09 12:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09  9:36 d_jan
2012-08-09 12:25 ` Stefan Müller [this message]
2012-08-09 18:36   ` d_jan
2012-08-09 12:26 ` Wolfgang Schuster

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=5023AC1C.7070401@gmx.de \
    --to=warrence.stm@gmx.de \
    --cc=d_jan@ymail.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).