| pod2man - Convert POD data to formatted *roff input |
pod2man - Convert POD data to formatted *roff input
pod2man [--center=string] [--date=string] [--errors=style] [--fixed=font] [--fixedbold=font] [--fixeditalic=font] [--fixedbolditalic=font] [--name=name] [--nourls] [--official] [--quotes=quotes] [--release[=version]] [--section=manext] [--stderr] [--utf8] [--verbose] [input [output] ...]
pod2man --help
pod2man is a front-end for Pod::Man, using it to generate *roff input from POD source. The resulting *roff code is suitable for display on a terminal using nroff(1), normally via man(1), or printing using troff(1).
input is the file to read for POD source (the POD can be embedded in
code). If input isn't given, it defaults to STDIN. output, if
given, is the file to which to write the formatted output. If output
isn't given, the formatted output is written to STDOUT. Several POD
files can be processed in the same pod2man invocation (saving module
load and compile times) by providing multiple pairs of input and
output files on the command line.
--section, --release, --center, --date, and --official can be used to set the headers and footers to use; if not given, Pod::Man will assume various defaults. See below or the Pod::Man manpage for details.
pod2man assumes that your *roff formatters have a fixed-width font
named CW. If yours is called something else (like CR), use
--fixed to specify it. This generally only matters for troff output
for printing. Similarly, you can set the fonts used for bold, italic, and
bold italic fixed-width output.
Besides the obvious pod conversions, Pod::Man, and therefore pod2man also
takes care of formatting func(), func(n), and simple variable references
like $foo or @bar so you don't have to use code escapes for them; complex
expressions like $fred{'stuff'} will still need to be escaped, though.
It also translates dashes that aren't used as hyphens into en dashes, makes
long dashes--like this--into proper em dashes, fixes ``paired quotes,'' and
takes care of several other troff-specific tweaks. See the Pod::Man manpage for
complete information.
STDIN.
die says to throw an exception on any
POD formatting error. stderr says to report errors on standard error,
but not to throw an exception. pod says to include a POD ERRORS
section in the resulting documentation summarizing the errors. none
ignores POD errors entirely, as much as possible.
The default is die.
CW. Some systems may want CR instead. Only matters for troff(1)
output.
CB. Only matters
for troff(1) output.
CI. Only matters for troff(1) output.
CB. Some
systems (such as Solaris) have this font available as CX. Only matters
for troff(1) output.
.../lib/Pod/Man.pm is converted
into a name like Pod::Man. This option, if given, overrides any
automatic determination of the name.
Note that this option is probably not useful when converting multiple POD files at once. The convention for Unix man pages for commands is for the man page title to be in all-uppercase even if the command isn't.
L<foo|http://example.com/>;
is formatted as:
foo <http://example.com/>;
This flag, if given, suppresses the URL when anchor text is given, so this
example would be formatted as just foo. This can produce less
cluttered output in cases where the URLs are not particularly important.
quotes may also be set to the special value none, in which case no
quote marks are added around C<> text (but the font is still changed for
troff output).
.TH macro. The standard section numbering
convention is to use 1 for user commands, 2 for system calls, 3 for
functions, 4 for devices, 5 for file formats, 6 for games, 7 for
miscellaneous information, and 8 for administrator commands. There is a lot
of variation here, however; some systems (like Solaris) use 4 for file
formats, 5 for miscellaneous information, and 7 for devices. Still others
use 1m instead of 8, or some mix of both. About the only section numbers
that are reliably consistent are 1, 2, and 3.
By default, section 1 will be used unless the file ends in .pm, in
which case section 3 will be selected.
--errors=stderr and is supported for backward compatibility.
X.
This option says to instead output literal UTF-8 characters. If your *roff implementation can handle it, this is the best output format to use and avoids corruption of documents containing non-ASCII characters. However, be warned that *roff source with literal UTF-8 characters is not supported by many implementations and may even result in segfaults and other bad behavior.
Be aware that, when using this option, the input encoding of your POD
source must be properly declared unless it is US-ASCII or Latin-1. POD
input without an =encoding command will be assumed to be in Latin-1,
and if it's actually in UTF-8, the output will be double-encoded. See
perlpod(1) for more information on the =encoding command.
As long as all documents processed result in some output, even if that
output includes errata (a POD ERRORS section generated with
--errors=pod), pod2man will exit with status 0. If any of the
documents being processed do not result in an output document, pod2man
will exit with status 1. If there are syntax errors in a POD document
being processed and the error handling style is set to the default of
die, pod2man will abort immediately with exit status 255.
If pod2man fails with errors, see the Pod::Man manpage and the Pod::Simple manpage for information about what those errors might mean.
pod2man program > program.1
pod2man SomeModule.pm /usr/perl/man/man3/SomeModule.3
pod2man --section=7 note.pod > note.7
If you would like to print out a lot of man page continuously, you probably want to set the C and D registers to set contiguous page numbering and even/odd paging, at least on some versions of man(7).
troff -man -rC1 -rD1 perl.1 perldata.1 perlsyn.1 ...
To get index entries on STDERR, turn on the F register, as in:
troff -man -rF1 perl.1
The indexing merely outputs messages via .tm for each major page,
section, subsection, item, and any X<> directives. See
the Pod::Man manpage for more details.
Lots of this documentation is duplicated from the Pod::Man manpage.
the Pod::Man manpage, the Pod::Simple manpage, man(1), nroff(1), perlpod(1), podchecker(1), perlpodstyle(1), troff(1), man(7)
The man page documenting the an macro set may be man(5) instead of man(7) on your system.
The current version of this script is always available from its web site at http://www.eyrie.org/~eagle/software/podlators/. It is also part of the Perl core distribution as of 5.6.0.
Russ Allbery <rra@stanford.edu>, based very heavily on the original pod2man by Larry Wall and Tom Christiansen.
Copyright 1999, 2000, 2001, 2004, 2006, 2008, 2010, 2012, 2013 Russ Allbery <rra@stanford.edu>.
This program is free software; you may redistribute it and/or modify it under the same terms as Perl itself.
| pod2man - Convert POD data to formatted *roff input |