Name

manuals - Format of manuals

Description

The ProLine Reference Manual consists of individual files, called entries, that describe a part of the system, be it a command, a file format, miscellaneous information, etc.

Manuals follow a specific visual format. Shown at the top of each page is an entry’s title and section, e.g. MANUALS(F), and at the bottom is its modification date, page number, and date printed.

Subheaders


These subheaders are standard in manual entries and typically follow in the order presented here:

Name

A short, one-line summary of the document follows.

Syntax

Included for entries that describe a command with parameter arguments.

Description

Begins the descriptive body of the entry. The body of an entry is generally undefined. Though, it should not use any subheader other than those described here. It may contain, however, its own paragraph headings.

Note

(or Notes, Bugs, Warning, Important, etc.) This subheader proceeds important information that should stand out from the body of the description, such as hazards or side effects.

Diagnostics

Error messages and their meanings.

Files

If any files are associated with an entry, they are listed after this subheader, usually near the end of the entry. Each file listed should include a short description.

See Also

Usually, an entry ends with a “See Also” subheader, followed by a reference list to related entries.

Author

(Optional). The name of the author (for the entry and/or the command it describes) is given, along with the author’s e-mail address. If this subheader is not included, it is assumed that the author is Morgan Davis.

Internal Structure


Manuals are punctuated with “dot” commands for interpretation by processing programs such as man and manps. Each command has the form of a period (.) followed by a two-letter command name. Arguments to a command are separated from the command by a space. Text that does not start with a period is considered text to be processed. Text portions need not be formatted in the source file, as the processing programs will perform all the necessary formatting.

Dot Commands


The “dot” commands are described below. In the descriptions, “s” denotes a set of characters while “n” denotes a number. Arguments shown between [ ] brackets are optional. If the optional number is omitted, zero is assumed, unless otherwise noted.

.TH s1 s2

Title Header. s1 is the entry’s title, followed by a space, and then the associated section, s2. Both arguments must be in uppercase. (e.g. .TH MANUALS F)

.DA s

Date. s contains the date of the last modification of the entry in this format: 12 March 1992.

.SH s

Subheader. Displays s fully left justified.

.LM [n]

Left Margin. The value of n is added to the current left margin. A negative value narrows the margin, while a positive value widens it.

.RM [n]

Right Margin. The value of n is added to the current right margin. A negative value narrows the margin, while a positive value widens it.

.PP [s]

New Paragraph (with optional s paragraph header).

.IP [n [s]]

Indented Paragraph. Begins a new paragraph, setting the indentation to n columns. If s is included, it is displayed at the left margin, and the print position tabs out to the indentation point. The effect is what you see here — the dot commands are left-margin justified, while the descriptions are indented. Use .IP with no arguments to disable indentation.

.CN s

Centers s, followed by line break.

.SP [n]

Spaces. Print n spaces (default is 1).

.RC [n] s

Repeat Character. Prints the s character n times. If n is omitted, s is repeated up to the right margin and a line break follows. Use this command to display characters that would be misinterpreted if included in text (e.g. “.RC 1 _ ”).

.BR [n]

Break. Inserts n line breaks (default is 1). This moves the printing position to the next line, respecting current indentation settings.

.AF [n]

Auto-Fill. If n is given, auto-fill is turned on (1) or off (0). If no argument is given auto-fill is toggled. Proceeding text lines are displayed with no formatting. Blank lines are ignored, but commands such as .BR are still recognized.

.UC [s]

Underline Character. Sets the emphasis-toggle character to s (default is the underscore ‘ _ ’). Text selections surrounded by this character are emphasized. For video displays, this results in either highlighted or underscored text. For dot matrix printers, the text is underlined. For PostScript devices, the text is italicized.

.NP

New Page. Ends the current page by printing the appropriate number of lines, followed by the page footer.

.IF n

If fewer than n lines remain on the page, a new page (.NP) is performed. Include .IF before tables or lists that should not be broken across pages. The .SH, .PP and .IP commands include built-in widow control, as if “.IF 2” precede them.

.TB n

Tab to column n from current print position.

An excellent way to learn to “program” a new manual entry is to compare the contents of an existing entry with its printed output, noting how each dot command effects the display.

Typographic Conventions


Whenever reference is made to the command being described by the entry, always highlight it using the underscore/highlight quoting character. Similarly, reference to other commands should be highlighted as well. Highlighting is valuable for making urgent or important passages of text stand out. Such text is displayed in italics on PostScript printers.

Use typographer’s quotation marks. These consist of the apostrophe (’) and accent grave (‘) characters, either singularly or in pairs. “Like this,” for example.

Whenever examples are used that reference items that the user might see on the screen, turn off the auto-fill mode (.AF). Text that is not auto-filled is displayed in Courier, a monospace font, on PostScript printers. This has a the desirable effect of making the text stand out in a “computer-like” typeface.

Files

$/sys/man/*
contains manual sections and entries.

See Also

man(CT), manps(CT), whatis(C)