| OXDOC(1) | General Commands Manual | OXDOC(1) |
NAME
oxdoc — format and
check manual pages
SYNOPSIS
oxdoc |
[-T device]
[-O
option[,option ...]]
[-W level]
[file ...] |
DESCRIPTION
The oxdoc utility formats manual pages
written in the mdoc(7) or
man(7) language, with tables
(tbl(7)) and equations
(eqn(7)), and in the
roff(7) requests and escapes that pages
use. It reads each file, or the standard input if none
is given, and writes the formatted page to the standard output.
The options are as follows:
-Ooption- Set output options, separated by commas:
width=columns- The line length. The default is the terminal's width, at most 80, less two; or 78 when the output is not a terminal.
overstrike- Show bold and underline as backspace overstrike
(‘
c\bc, ‘’) rather than as terminal escape sequences, for pagers and col(1)._\bc’ plain- No bold or underline at all.
os=name- The operating system name for a page whose
Osmacro has no argument.
-Tdevice- The output device:
-Wlevel- Report diagnostics at level and above:
style,warning(the default),errororunsupp.allisstyle;stopstops after the first file with a diagnostic at the chosen level.
Bold and underline are shown when the output is a terminal, as SGR escape sequences, and not otherwise.
ENVIRONMENT
LC_ALL,LC_CTYPE,LANG- The first of these that is set decides the default device:
utf8if it names UTF-8,asciiotherwise.
EXIT STATUS
- 0
- No diagnostic at
warninglevel or above. - 1
- At least one such diagnostic.
- 2
- A usage error, or a file could not be read.
DIAGNOSTICS
Diagnostics have the form
oxdoc:
file:line:column:
LEVEL: message:
detailSEE ALSO
STANDARDS
The output follows the formatting of mandoc(1), which the other BSDs use.
HISTORY
The oxdoc utility was written for
OxideBSD.
BUGS
The HTML and Markdown devices are not implemented yet.
| September 28, 2026 | OxideBSD |