From: madcrow.maxwell@gmail.com (Michael Kerpan)
Subject: [TUHS] IANAL. Kimball has ruled
Date: Thu, 17 Jul 2008 13:32:22 -0400 [thread overview]
Message-ID: <8dd2d95c0807171032l76674668v7df1ae9a6fb938a8@mail.gmail.com> (raw)
In-Reply-To: <20080717172732.GK19812@bitmover.com>
On Thu, Jul 17, 2008 at 1:27 PM, Larry McVoy <lm at bitmover.com> wrote:
> On Thu, Jul 17, 2008 at 01:12:05PM -0400, John Cowan wrote:
>> Indeed, both ditroff and Plan 9 troff are directly descended from
>> JFO's code. Only groff is independent, which just goes to show what a
>> heroic programmer (in a quiet way) James Clark really is (as do nsgmls
>> and jing/trang).
>
> As a still-using-troff sort of person, I can vouch for James. Wow.
> Cool stuff. And groff really is mucho better than the original.
Perhaps, but it's not as good as Heirloom Troff, which is based on the
"real" sources, but adds lots of groff's features PLUS adds a new font
system that allows for the trasparent use of unmodified Type 1,
Truetype and even OpenType (including all the fancy stuff) fonts AND
tweaks the various typesetting algorithms for MUCH nicer results.
next prev parent reply other threads:[~2008-07-17 17:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 8:18 Jose R. Valverde
2008-07-17 15:55 ` Gregg C Levine
2008-07-17 15:58 ` Larry McVoy
2008-07-17 16:18 ` Bryan Cantrill
2008-07-17 17:12 ` John Cowan
2008-07-17 17:27 ` Larry McVoy
2008-07-17 17:32 ` Michael Kerpan [this message]
2008-07-17 16:33 ` Boyd Lynn Gerber
2008-07-17 17:04 ` Wilko Bulte
2008-07-17 20:51 ` Michael Davidson
[not found] <mailman.1871.1216314893.89381.tuhs@minnie.tuhs.org>
2008-07-17 19:55 ` Pepe
2008-07-17 20:22 ` Bryan Cantrill
2008-07-17 22:30 ` Pepe
2008-07-17 20:40 ` Boyd Lynn Gerber
2008-07-18 14:10 ` Jose R. Valverde
2008-07-18 17:03 Michael Davidson
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=8dd2d95c0807171032l76674668v7df1ae9a6fb938a8@mail.gmail.com \
--to=madcrow.maxwell@gmail.com \
/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).