1 .\" Copyright (c) 1980, 1990, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. All advertising materials mentioning features or use of this software
13 .\" must display the following acknowledgement:
14 .\" This product includes software developed by the University of
15 .\" California, Berkeley and its contributors.
16 .\" 4. Neither the name of the University nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .\" @(#)checknr.1 8.1 (Berkeley) 6/6/93
40 .Nd check nroff/troff files
43 .Op Fl a Ns Ar \&.x1.y1.x2.y2. ... \&.xn.yn
44 .Op Fl c Ns Ar \&.x1.x2.x3 ... \&.xn
54 input files for certain kinds of errors
55 involving mismatched opening and closing delimiters
57 If no files are specified,
59 checks the standard input.
64 Add additional pairs of macros to the list of known macros.
65 This must be followed by groups of six characters, each group defining
67 The six characters are
71 and the second macro name.
72 For example, to define a pair .BS and .ES, use
75 Define commands which would otherwise be complained about
89 Delimiters checked are:
92 Font changes using \efx ... \efP.
94 Size changes using \esx ... \es0.
96 Macros that come in open ... close forms, for example,
97 the .TS and .TE macros which must always come in pairs.
101 is intended for use on documents that are prepared with
103 in mind, much the same as
105 It expects a certain document writing style for
112 must be terminated with
117 must be terminated with
119 While it will work to directly go into the next font or explicitly
120 specify the original font or point size,
121 and many existing documents actually do this,
122 such a practice will produce complaints from
124 Since it is probably better to use the
129 you should think of this as a contribution to your document
146 Complaints about unmatched delimiters.
147 Complaints about unrecognized commands.
148 Various complaints about the syntax of commands.
151 There is no way to define a 1 character macro name using
154 Does not correctly recognize certain reasonable constructs,
155 such as conditionals.