Certainly works -- thanks Wolfgang. Stymies me how people on this mailing list know this stuff -- even a Google search for "setbreakpoints", assuming I knew the command in advance, returns nada. James On Wed, Mar 3, 2010 at 7:36 PM, Wolfgang Schuster < schuster.wolfgang@googlemail.com> wrote:

Am 03.03.10 20:19, schrieb James Fisher:

Hi,

...

I'm experiencing an issue where, when the width of a block of text is small, the occasional word sticks out from the otherwise flush right. I've previously seen an example of this in an image on the contextgarden wiki, but now can't find it. To reproduce what I mean, compile this with Mark IV:

\mainlanguage[en] \usetypescript[palatino] \setupbodyfont[palatino,11pt]

In this case you don't need \usetypescript.

\setuppapersize[A4][A4]

...

\setuphead[title][header=empty]

\starttext \title{Personal statement}

\startcolumns[n=2] This heavily-hyphenated jauntily-formatted flush-left flush-right justified-text paragraph set in a two-column layout and subtly-quirky-but-never-offensive Palatino shouldn't produce out-of-flush sticking-out-like-a-sore-thumb words from the flush-right. \stopcolumns \stoptext

In this example, the string 'sticking-out-like-a-sore-thumb' sticks out to approx 3mm from the right edge of the paper. In this situation, I would much prefer that that string is hyphenated, using one of the hyphens already in the string.

Based on one other test (in which my text was far less hyphenated than the above), it seems that the hyphenation algorithm refuses to hyphenate strings of words that are already hyphenated. Is this true? If so, is it deliberate? And how do I turn it off? (And do other people agree with me that it's awfully ugly?)

Add \setbreakpoints[compound] to your file.

Wolfgang

___________________________________________________________________________________ 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

___________________________________________________________________________________

I suppose because (1) The word 'breakpoint' didn't come to mind (2) I'm used to consulting documentation rather than source code in the first instance (3) I've never worked in Turing tarpits before (4) Grepping 'breakpoint' as suggested doesn't turn up anything obvious in any case -- about 100 instances any of which could be a lead. I'm getting the impression that there's no real-world distinction between ConTeXt users and ConTeXt developers. James On Wed, Mar 3, 2010 at 8:44 PM, luigi scarso wrote:

On Wed, Mar 3, 2010 at 9:41 PM, James Fisher wrote:

...

Certainly works -- thanks Wolfgang.

Stymies me how people on this mailing list know this stuff -- even a Google search for "setbreakpoints", assuming I knew the command in advance, returns nada. So why don't you grep in base/* ?

-- luigi

___________________________________________________________________________________ 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

___________________________________________________________________________________