Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cmcl2!rna!dan
From: dan@rna.UUCP (Dan Ts'o)
Newsgroups: comp.text
Subject: Re: What features would you like in GNU troff?
Message-ID: <641@rna.UUCP>
Date: 9 Jun 89 18:30:11 GMT
References: <JJC.89May31220314@jclark.UUCP> <622@rna.UUCP> <22@nx32s.anduk.co.uk>
Reply-To: dan@rna.UUCP (Dan Ts'o)
Distribution: comp
Organization: Rockefeller University Neurobiology
Lines: 15

In article <22@nx32s.anduk.co.uk> lee@nx32s.UUCP (0000-Liam R. Quin) writes:
)In article <622@rna.UUCP> dan@rna.UUCP (Dan Ts'o) writes:
))In article <JJC.89May31220314@jclark.UUCP> jjc@jclark (James Clark) writes:
))	I implemented a NROFF-like program for "typesetting" BRAILLE (also
))does ASCII, source compatible with NROFF/TROFF). For long names, I used
))\{nameofanylength}. Of course macros can be of any length, and builtin
))commands also had more friendly aliases, like .space and .break and .page
))can be used for .sp, .br and .bp.
)The only trouble with this is that you can't have long special
)symbols like \{pound-sterling} or \{dagger}, because \{ already means
)the "then" of an if-then-else, and is legal in generally the same places.

	Sorry, I typed that in wrong. Its \*{long-string-name} for strings,
and \n{long-number-register-name} for number registers. Macros, of course,
can also have long names.