NAME

SYNOPSIS

checknr [-fs] [-a.x1.y1 .x2.y2. ... .xn.yn] [-c.x1.x2.x3 ... .xn] [file ...]

DESCRIPTION

(1)

Font changes using \fx ... \fP.

(2)

Size changes using \sx ... \s0.

(3)

Macros that come in open ... close forms, for example, the .TS and .TE macros which must always come in pairs.

Checknr knows about the ms(7) and me(7) macro packages.

Additional pairs of macros can be added to the list using the -a option. This must be followed by groups defining pairs of macros. The characters in each group 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

The -c option defines commands which would otherwise be complained about as undefined.

The -f option requests checknr to ignore \f font changes.

The -s option requests checknr to ignore \s size changes.

Checknr 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 directly go into the next font or explicitly specify the original font or point size, and many existing documents actually do this, such a practice will produce complaints from checknr. Since it is probably better to use the \fP and \s0 forms anyway, you should think of this as a contribution to your document preparation style.

SEE ALSO

DIAGNOSTICS

NOTES