NAME
checknr - Checks nroff and troff files
SYNOPSIS
checknr [-fs] [-a.x1.y1.x2.y2 ... .xn.yn] [-c.x1.x2.x3 ...
.xn] [file ...]
The checknr command checks a list of nroff or troff input
files (see RELATED INFORMATION) for certain kinds of errors
involving mismatched opening and closing delimiters and
unknown commands.
FLAGS
-a.x1.y1.x2.y2 ... .xn.yn
Adds pairs of macros to the list. This flag must be
followed by groups of six characters, each group defin-
ing a pair of macros. The six characters are a period,
the first macro name, another period, and the second
macro name. For example, to define a pair .BS and .ES,
use -a.BS.ES. (You cannot use the -a flag to define a
1-character macro name.)
-c.x1.x2.x3 ... .xn
Defines otherwise undefined commands.
-f Causes checknr to ignore \f font changes.
-s Causes checknr to ignore \s size changes.
DESCRIPTION
If no files are specified, checknr checks the standard
input. Delimiters checked are as follows:
o Font changes using \fx ... \fP.
o Size changes using \sx ... \s0.
o Macros that come in open/close forms (for example, the
.TS and .TE macros), which must always come in pairs.
The checknr command can handle both the ms and me macro
packages.
The checknr command is intended to be used on documents that
are prepared with checknr in mind, much the same as lint.
It expects a certain document writing style for \f and \s
commands, in that each \fx must be terminated with \fP and
each \sx must be terminated with \s0. While it will work to
go directly into the next font or explicitly specify the
original font or point size, and many existing documents
actually do this, such a practice produces error messages
from checknr.
The checknr command does not recognize certain reasonable
constructs, such as conditionals.
RELATED INFORMATION
The nroff, troff, tbl, deroff, eqn, neqn, checkeq, and
checkmm commands may be available on your system, but are
not provided with OSF/1.
Acknowledgement and Disclaimer