ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Marco Patzer <homerow@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: About Hyphenation
Date: Wed, 24 Jul 2013 21:34:33 +0200	[thread overview]
Message-ID: <20130724193433.GB24584@homerow> (raw)
In-Reply-To: <20891425-1740-4DE2-9D26-37219CA78BE7@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1308 bytes --]

On 2013–07–24 Wolfgang Schuster wrote:

> > Apparently \brokenpenalty is not supposed to be used with
> > \setpenalties, see spac-ver.mkiv :
> > 
> >    \setpenalties\widowpenalties\plustwo\maxdimen
> >    \setpenalties\clubpenalties \plustwo\maxdimen
> >                 \brokenpenalty         \maxdimen
> > 
> > Actually I don't yet know what's the deal with the \setpenalties
> > command and why it's used for some penalties and not for others.
> 
> You have to differ between the \…penalty command which come
> from Knuths TeX and \…penalties which are introduced with etex.
> 
> While Knuths command accept only a single value (e.g. \widowpenlty=1000)
> the new commands accepts multiple values which are taken for individual
> lines of a paragraph (e.g. \widowpenalties 3 3000 4500 9000).

I learned something new today.

> The \setpenalties command simplifies the setups of the new commands.

Combined with the aforementioned new knowledge, this totally makes
sense.

> The reason why \widowpenalties doesn’t work with \setpenalties is that
> no command with this names exist (I never checked this for my example
> in the past).

I couldn't find the definition neither in the TeXbook, nor the
ConTeXt sources. That's why. Thanks for the explanation.

Marco

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 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
___________________________________________________________________________________

  reply	other threads:[~2013-07-24 19:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24 18:22 Andres Conrado Montoya
2013-07-24 18:44 ` Wolfgang Schuster
2013-07-24 18:54   ` Marco Patzer
2013-07-24 19:15     ` Wolfgang Schuster
2013-07-24 19:34       ` Marco Patzer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-07-25  1:24 Andres Conrado Montoya
2013-07-25  7:49 ` Hans Hagen
2013-07-23 21:28 Andres Conrado Montoya
2013-07-23 22:07 ` Marco Patzer

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=20130724193433.GB24584@homerow \
    --to=homerow@lavabit.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).