Hello *roffers,
I recently needed to include the succeeds character - u227B - in an eqn
equation, e.g.:
n ≻ sqrt n
I don't know of a Groff default font that includes it, but it appears in
the Symbola font that I installed using Schaffter's install-font.sh. I
include it in the file with:
.
> I was wondering if some kind of pre-processor existed back in the time
Yes, "form" and "fed", a form-letter generator and editor, were in the 2nd
through 6th editions of Unix. Created by Bob Morris and Lorinda Cherry,
they were independent of roff, but could of course could produce roff
input. Y
Hi Branden,
> The \z+o status quo seems to follow a pattern that makes sense for
> modified letterforms, i.e., \z'a; on a 7-bit ASCII, non-overstriking
> device, you want the "a" to "win", because it carries the more
> important semantic information.
Agreed.
> That reasoning does not hold for bu
On Thursday, March 28, 2019 3:01 AM, G. Branden Robinson wrote:
> At 2019-03-27T04:34:18+, Jeff Conrad wrote:
> > Is there a reason that tty.tmac translates \(bu to \(pc or \(md
> > regardless of the output device or whether \(bu is available?
> >
> > .ie c\[pc] \
> > . tr \[bu]\[pc]
> > .el
At 2019-03-27T04:34:18+, Jeff Conrad wrote:
> Is there a reason that tty.tmac translates \(bu to \(pc or \(md
> regardless of the output device or whether \(bu is available?
>
> .ie c\[pc] \
> . tr \[bu]\[pc]
> .el \
> . if c\[md] \
> .tr \[bu]\[md]
Are you looking at an old implementat
Hello Robert,
Robert Thorsby wrote:
> Why not simply use groff as *one* of the tools to do the job? In your
> favourite programming/scripting language extract the data from the
> various sources and dump those extracts into a template that contains
> all the groff information.
That's the kind
