ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Ed L Cashin <ecashin@coe.uga.edu>
Cc: Hraban <angerweit@gmx.net>, ConTeXt <ntg-context@ntg.nl>
Subject: Re: (no) hyphenation
Date: 19 Jul 2000 08:56:44 -0400	[thread overview]
Message-ID: <m3em4qnur7.fsf@coe.uga.edu> (raw)
In-Reply-To: Hans Hagen's message of "Wed, 19 Jul 2000 09:13:50 +0200"

Hans Hagen <pragma@wxs.nl> writes:

> At 01:28 AM 7/18/00 +0200, Hraban wrote:
> 
> >And I thought, TeX would be able to do *everything* ...
> >(Telling so myself to the people)
>
> I can assure you that there are many thinks tex cannot do. You would
> be surprised to see how much time is spent on programming things
> that seem simple. Did you know that tex cannot do double columns?
> You can fake them, which is what happens.

I know it must be very difficult to fake multiple-column output,
because so many macropackages have trouble with this feature.  This is
off topic, but I'm curious to know: do the new typesetting projects
like omega and NTS have built-in multicolumn support?

> There are also things tex can do that people think tex cannot
> do. The metafun manual I'm working on shows some.

Yes, but that's cheating, because you are finding ways to have TeX and
MetaPost dancing gracefully together!  TeX alone would not be such a
show stopper on the graphics dance floor.

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


  reply	other threads:[~2000-07-19 12:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-14 21:10 Hraban
2000-07-17  0:45 ` Hans Hagen
2000-07-17 23:28   ` Hraban
2000-07-19  7:13     ` Hans Hagen
2000-07-19 12:56       ` Ed L Cashin [this message]
2000-07-19 14:36         ` Hans Hagen
2000-07-24 20:20       ` metafun Hraban

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=m3em4qnur7.fsf@coe.uga.edu \
    --to=ecashin@coe.uga.edu \
    --cc=angerweit@gmx.net \
    --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).