ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Occasional words sticking out from flush-right
Date: Thu, 4 Mar 2010 18:36:49 -0500 (EST)	[thread overview]
Message-ID: <alpine.LNX.2.01.1003041834150.26485@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <771da05a1003041531p74f2857awb1e95ff57ee3bd3a@mail.gmail.com>

On Thu, 4 Mar 2010, James Fisher wrote:

> I'd like to go back to the very first post about problems with flush right.
> The \setbreakpoints command works to an extent, but I'm still experiencing
> issues where, when a hyphenated string has been broken, the first half of it
> still sticks out.  I unfortunately can't show you the example, and it's hard
> to reproduce.  But can anyone answer: does the TeX line-breaking algorithm
> retain the possibility of lines overrunning the defined boundary, if the
> algorithm decides that the alternatives are more ugly?

Yes.

Try \setuptolerance[tolerant] or \setuptolerance[verytolerant].

Aditya
___________________________________________________________________________________
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:[~2010-03-04 23:36 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.607.1267648881.26807.ntg-context@ntg.nl>
2010-03-03 21:47 ` Vyatcheslav Yatskovsky
2010-03-03 21:53   ` Arthur Reutenauer
2010-03-03 23:19     ` James Fisher
2010-03-04  0:08       ` Aditya Mahajan
2010-03-04  2:35         ` James Fisher
2010-03-04  4:06           ` Aditya Mahajan
2010-03-04 14:39             ` James Fisher
2010-03-04 17:11               ` Aditya Mahajan
2010-03-04 17:15                 ` luigi scarso
2010-03-04 17:30                   ` Aditya Mahajan
2010-03-04 18:43                     ` luigi scarso
2010-03-04 17:50                 ` James Fisher
2010-03-04  7:10           ` luigi scarso
2010-03-04 14:25             ` James Fisher
2010-03-04 18:42               ` luigi scarso
2010-03-04 19:44                 ` James Fisher
2010-03-04 20:04                   ` Aditya Mahajan
2010-03-04 20:47                   ` luigi scarso
2010-03-04 23:31                     ` James Fisher
2010-03-04 23:36                       ` Aditya Mahajan [this message]
2010-03-04 23:47                         ` James Fisher
2010-03-05  9:30                   ` luigi scarso
2010-03-03 23:09 ` setbreakpoints Vyatcheslav Yatskovsky
2010-03-04 14:40   ` setbreakpoints James Fisher
2010-03-03 19:19 Occasional words sticking out from flush-right James Fisher
2010-03-03 19:36 ` Wolfgang Schuster
2010-03-03 20:41   ` James Fisher
2010-03-03 20:44     ` luigi scarso
2010-03-03 21:19       ` James Fisher
2010-03-03 22:46         ` luigi scarso

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=alpine.LNX.2.01.1003041834150.26485@ybpnyubfg.ybpnyqbznva \
    --to=adityam@umich.edu \
    --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).