ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: line breaking hints?
Date: Tue, 27 Nov 2007 09:40:04 +0100	[thread overview]
Message-ID: <474BD7E4.7050100@elvenkind.com> (raw)
In-Reply-To: <6703815B292B664DBAEC55EE3192386A20BCD0@poseidon.in.dynetics.com>

Santy, Michael wrote:
> Hello,
> 
> I'm looking for a way to give ConTeXt's line breaking algorithm a
> hint on where it is allowed to break a line.  For example, I want
> ConTeXt to break lines, if necessary, when it encounters '//' in a
> string.  I don't want to force a line break there, but if context
> needs to break the line, I want it to be after a "//".

I've been trying various things, but so far I have failed to find
a general solution to do this.

Normally you would say something like "\penalty-100" to hint that
some place is a good place to break a line, but such a hint is never
exclusive: TeX will happily use breakpoints elsewhere if those appear
to be better to the line breaking algorithm.

That's why you would need something like:

   \def\\{\hskip0pt plus .5\hsize \penalty-100 \hskip0pt plus -.5\hsize}

to make the break more attractive. The downside is that this actually
works by based on the 'break width' of the line, and because it will
not prevent other breaks, the break above will always be taken if the
current to-be-broken line is half-full or more already (so a line
that may actually fit on one line can be broken in two).

Anyway, as you don't mind ragged right typesetting, this should work
more or less:

   \def\specialpar#1%
     {\begingroup
      \rightskip=0pt plus \hsize
      \linepenalty100
      \clubpenalty0\widowpenalty0
      \hyphenpenalty10000\exhyphenpenalty10000
      \def\\{\penalty-50}%
      #1\endgraf
      \endgroup}

   \specialpar{HE QUICK BROWN FOX JUMPED OVER THE LAZY DOG//\\ NOW IS THE
    TIME FOR ALL GOOD MEN TO COME TO THE AID OF THEIR COUNTRY.}

Note I've added a special macro \\, instead of attemping to automate
breaking after //.

This 'solution' is far from perfect, but the problem is simply hard.

Best wishes,
Taco

___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2007-11-27  8:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-26 21:08 Santy, Michael
2007-11-27  8:40 ` Taco Hoekwater [this message]
2007-11-27 13:39   ` Santy, Michael
2007-11-27  8:50 ` 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=474BD7E4.7050100@elvenkind.com \
    --to=taco@elvenkind.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).