ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: ecashin@coe.uga.edu (Ed L. Cashin)
Subject: "A complex index" in _Digital Typography_
Date: 15 Nov 1999 15:17:35 -0500	[thread overview]
Message-ID: <m3zowfa4rk.fsf@kali.coe.uga.edu> (raw)

Hi.  In reading Knuth's _Digital Typography_ at lunch today, I came
across a section of the "Breaking Paragraphs into Lines" chapter that
relates directly to a difficulty in a project I'm doing.

In the section "A complex index", pp. 98ff., it describes a way to do
line breaking on an index entry such that the "name" part (on the
left) is ragged right and the "reference" part (on the right) is
ragged left, like this:

      |                                                       |
      | foo bar baz and even more........... 1100, 2000, 3300 |
      |                                                       |

      |                                      |
      | foo bar baz and even more ......     | 
      |                     1100, 2000, 3300 |
      |                                      |

      |                      |
      | foo bar baz and      |
      |    even more         |
      |     .... 1100, 2000, |
      |                 3300 |
      |                      |

I was planning on using perl to doctor the input text so that such
complex line-breaking decisions were unnecessary, but I'm wondering
now whether this might be something that people have already tackled. 

Is there support in ConTeXt for such complex line breaking strategies?
The criteria Knuth (and Plass) describe in the "A complex index"
section are pretty involved.

-- 
--Ed Cashin                     PGP public key:
  ecashin@coe.uga.edu           http://www.coe.uga.edu/~ecashin/pgp/


             reply	other threads:[~1999-11-15 20:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-15 20:17 Ed L. Cashin [this message]
1999-11-16  9:24 ` Hans Hagen
1999-11-16 11:18 ` Taco Hoekwater

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=m3zowfa4rk.fsf@kali.coe.uga.edu \
    --to=ecashin@coe.uga.edu \
    /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).