Computer Old Farts Forum
 help / color / mirror / Atom feed
From: ralph at inputplus.co.uk (Ralph Corderoy)
Subject: [COFF] roff vs. Tex (was: Looking for final C compiler by Dennis Ritchie)
Date: Tue, 24 Jul 2018 11:00:41 +0100	[thread overview]
Message-ID: <20180724100041.9B2B0214E0@orac.inputplus.co.uk> (raw)
In-Reply-To: <20180724035206.GA87618@eureka.lemis.com>

Hi Greg,

> Still, TeX has one significant advantage over [gt]roff that I'm aware
> of: it adjusts paragraphs, not lines, and it seems that in some cases
> this give better looking layout.

Gunnar Ritter's Hierloom troff, a descendent of OpenSolaris's, can
adjust paragraphs rather than lines.
http://heirloom.sourceforge.net/doctools.html

Ali Gholami Rudi's neatroff, a troff re-implementation, adjusts
paragraphs.  Search for `paragraph-at-once' at http://litcave.rudi.ir/
or http://litcave.rudi.ir/neatroff.pdf

There could be others.

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy


  parent reply	other threads:[~2018-07-24 10:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8ECDA62D-1B54-4391-A226-D3E9ABEE4C07@planet.nl>
     [not found] ` <CACXZuxeJ3igMtfbLs1iUPMLhomQUG0dEjpaHHmV0L7hF0bvo4g@mail.gmail.com>
     [not found]   ` <CAC20D2OTsR0ZxqeUk2EBpZnWy2k4LVf8=VPKzitWhkT3n_vL8g@mail.gmail.com>
     [not found]     ` <20180723155552.GB19635@mcvoy.com>
2018-07-23 16:41       ` [COFF] [TUHS] Looking for final C compiler by Dennis Ritchie crossd
2018-07-24  3:52         ` [COFF] roff vs. Tex (was: Looking for final C compiler by Dennis Ritchie) grog
2018-07-24  4:01           ` lm
2018-07-24 14:43             ` cym224
2018-07-24 10:00           ` ralph [this message]
2018-07-27  1:04             ` lm
2018-07-25 21:24           ` perry
2018-07-26  4:22             ` grog
2018-07-26  6:38               ` bakul
2018-07-26 12:22               ` perry
2018-07-27  1:28                 ` grog
2018-07-27  2:52                   ` cym224

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=20180724100041.9B2B0214E0@orac.inputplus.co.uk \
    --to=coff@minnie.tuhs.org \
    /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).