Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!brutus.cs.uiuc.edu!ginosko!uunet!mcsun!hp4nl!botter!star.cs.vu.nl!ast
From: ast@cs.vu.nl (Andy Tanenbaum)
Newsgroups: comp.os.minix
Subject: Re: An nroff clone
Message-ID: <3252@ast.cs.vu.nl>
Date: 13 Sep 89 21:48:51 GMT
References: <23660@louie.udel.EDU> <4671@hall.cray.com>
Reply-To: ast@cs.vu.nl (Andy Tanenbaum)
Organization: VU Informatica, Amsterdam
Lines: 19

In article <4671@hall.cray.com> rosenkra@hall.UUCP (Bill Rosenkranz) writes:
>In article <23660@louie.udel.EDU> mcd@ccsitn.att.com writes:
>i have been playing around with the nro posted. i have added .fl, .ec, .ft,
>.ll, .pn, .lt, .c2, .tl, .af, .ad, .na and several of the internal registers.
>i also fixed macro definition to include handling \\, \n, etc correctly.

WONDERFUL!  I think that text processing is one area where MINIX is very
deficient.  An improved nro would be a big plus.

One personal request.  I use \fR \fB and \fI all over the place.  It would
be nice if nro could handle them as regular, overstriking, and underlining,
respectively.  Another very useful feature would be .if .  I have macro
packages that are actually for troff, but I could easily test
.if n
to see if it is nroff, and proceed differently.

If you make enough progress, I might even rename nro back to nroff (again).

Andy Tanenbaum (ast@cs.vu.nl)