From: Ed L Cashin <ecashin@coe.uga.edu>
Cc: NTG-ConTeXt mailing list <ntg-context@ntg.nl>
Subject: Re: river detection
Date: 10 Jan 2001 13:59:31 -0500 [thread overview]
Message-ID: <m3puhv8c8c.fsf@coe.uga.edu> (raw)
In-Reply-To: Hans Hagen's message of "Wed, 10 Jan 2001 18:38:13 +0100"
Hans Hagen <pragma@wxs.nl> writes:
> At 11:58 AM 1/10/01 -0500, Ed L Cashin wrote:
>
> >But you could just do a TeX macro that expands to a kind of matrix
> >like this:
> >
> > (5, 6) (11, 15) (35, 40)
> > (7, 9) (11, 15) (26, 30)
> > (2, 4) (11, 14) (24, 26)
> >
> >(there's a river at position eleven).
>
> Eh ... when tex typesets a paragraph, all input is already converted to
> lists and macro expansion is gone. So, bbox info should come from the list
> to dvi pass [or maybe from within the paragraph builder]. Keep in mind that
> f i e t s [bicycle] is not just 5 chars, but becomes fi e t s and that at
> some point the hyphenation engine pops in too. No way to hyphenate
> \hbox{f}\hbox{i}...\hbox{s}.
I don't know what you mean by "the list to dvi pass".
Within the paragraph builder, though, I'm thinking that there's a time
when TeX tries a certain paragraph configuration. At that time, you
have information about where the horizontal glue between hboxes begins
and ends. That's the information that I was talking about in my
example. With "I w u v fi e t s", TeX knows that there's a good
bit of horizontal glue after the "v" box and before the "fi" box. It
knows the leftmost and rightmost position of that glue, right?
I was thinking that the river badness can be calculated at that time,
but are you saying that it can't be calculated at that time by a macro
because all the macro expansion is not going on at that time?
--
--Ed Cashin PGP public key:
ecashin@coe.uga.edu http://www.coe.uga.edu/~ecashin/pgp/
next prev parent reply other threads:[~2001-01-10 18:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 18:45 Ed L Cashin
2001-01-10 8:27 ` Hans Hagen
2001-01-10 16:58 ` Ed L Cashin
2001-01-10 17:38 ` Hans Hagen
2001-01-10 18:59 ` Ed L Cashin [this message]
2001-01-11 7:56 ` Hans Hagen
2001-01-11 20:21 ` Ed L Cashin
2001-01-12 14:57 ` H. Ramm
2001-01-10 10:40 ` Frans Goddijn
2001-01-10 11:29 ` Dan Seracu
2001-01-10 11:58 ` Hans Hagen
2001-01-10 11:57 ` Hans Hagen
2001-01-10 13:14 ` Taco Hoekwater
2001-01-10 14:04 ` Hans Hagen
2001-01-10 21:07 ` H. Ramm
[not found] <Hans Hagen's message of "Wed, 10 Jan 2001 18:38:13 +0100">
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=m3puhv8c8c.fsf@coe.uga.edu \
--to=ecashin@coe.uga.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).