From: Ed L Cashin <ecashin@coe.uga.edu>
Subject: river detection
Date: 09 Jan 2001 13:45:01 -0500 [thread overview]
Message-ID: <m3bstgd0pe.fsf@coe.uga.edu> (raw)
Han The Thanh discusses in his thesis several problems that computer
typography systems face. One problem that no current systems address
is "rivers", visual lines of blank space like this:
XXXXXXXXX XXXXXXXXXXXXXX XXXXXXXXX XXXXXXXX
XXXXXXX xxXX XXXXXXXX Xxxxx XXXXXX XXXXX
XX XXX XXXXXXX XXXXXX XXXXX XXXXXXXX XXXX
XXXXXXX XXXX XXXXXXX XXXX XXXXXXXX XXXXXXX
XXX XX XXXXXXX XXXXXX XXXXX XXXXXXXX XXXXX
XXXXX xxXX XXXXXXXX Xxxxx XXXXXX XXXXX X
XXXX XXX XXXXXXX XXXX XXXXXXXX XXXXXXX XX
... where there's a river on the left. Hans has been doing many
experiments combining MetaPost and TeX, where they share more
information about the visual appearance of the typeset text than has
traditionally been available.
Would it be possible to use MP and TeX together in order to detect
rivers? If so, it would be a computer typesetting first, according to
Thanh's thesis. :)
--
--Ed Cashin PGP public key:
ecashin@coe.uga.edu http://www.coe.uga.edu/~ecashin/pgp/
next reply other threads:[~2001-01-09 18:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 18:45 Ed L Cashin [this message]
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
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=m3bstgd0pe.fsf@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).