Section 1: user commands and tools
NAME pod2usage – print usage messages from embedded pod docs in files SYNOPSIS pod2usage [-help] [-man] [-exit exitval] [-output outfile] [-verbose level] [-pathlist dirlist] [-formatter module] [-utf8] file OPTIONS AND ARGUMENTS -help Print a brief help message and exit. -man Print this command’s manual page and exit. -exit exitval The exit status value to return. -output outfile…
NAME pod2text – Convert POD data to formatted ASCII text SYNOPSIS pod2text [-aclostu] [–code] [–errors=style] [-i indent] [-q quotes] [–nourls] [–stderr] [-w width] [input [output …]] pod2text -h DESCRIPTION pod2text is a front-end for Pod::Text and its subclasses. It uses them to generate formatted ASCII text from POD source. It can optionally use either termcap sequences or ANSI color escape sequences to…
NAME pod2texi – convert Pod to Texinfo SYNOPSIS pod2texi [OPTION]… POD… DESCRIPTION Translate Pod file(s) to Texinfo. There are two basic modes of operation. First, by default, each pod is translated to a standalone Texinfo manual. Second, if "–base-level" is set higher than 0, each pod is translated to a file suitable for @include, and…
NAME pod2test – Convert embedded tests and code examples to .t files SYNOPSIS pod2test[-Mmodule][input[output]] DESCRIPTION pod2test is a front-end for Pod::Tests (formerly Test::Inline 1). It generates TAP-compatible .t testing scripts from embedded tests and code examples. If output is not specified, the resulting .t file will go to STDOUT. Otherwise, it will go to the…
NAME pod2readme – script to convert POD to README file SYNOPSIS pod2readme lib/Some/Module.pm DESCRIPTIONS Converts POD in the specified file to a README text file. If a second argument is given, it will use that as the output file and assume that is the type of file to export: pod2readme Module.pm COPYING If need be,…
NAME pod2markdown – Convert POD text to Markdown VERSION version 2.002 SYNOPSIS # parse STDIN, print to STDOUT $ pod2markdown < POD_File > Markdown_File # parse file, print to STDOUT $ pod2markdown input.pod # parse file, print to file $ pod2markdown input.pod output.mkdn # parse STDIN, print to file $ pod2markdown – output.mkdn DESCRIPTION This…
NAME pod2man – Convert POD data to formatted *roff input SYNOPSIS pod2man [–center=string] [–date=string] [–errors=style] [–fixed=font] [–fixedbold=font] [–fixeditalic=font] [–fixedbolditalic=font] [–name=name] [–nourls] [–official] [–release=version] [–section=manext] [–quotes=quotes] [–lquote=quote] [–rquote=quote] [–stderr] [–utf8] [–verbose] [input [output] …] pod2man –help DESCRIPTION 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…
NAME pod2latex – convert pod documentation to latex format SYNOPSIS pod2latex *.pm pod2latex -out mytex.tex *.pod pod2latex -full -sections ‘DESCRIPTION|NAME’ SomeDir pod2latex -prefile h.tex -postfile t.tex my.pod DESCRIPTION "pod2latex" is a program to convert POD format documentation (perlpod) into latex. It can process multiple input documents at a time and either generate a latex file…
NAME pod2html – convert .pod files to .html files SYNOPSIS pod2html– help– htmldir = <name> –htmlroot = <URL> –infile = <name> –outfile = <name> –podpath = <name> : … : <name> –podroot = <name> –cachedir = <name> –flush– recurse– norecurse– quiet– noquiet– verbose– noverbose– index– noindex– backlink– nobacklink– header– noheader– poderrors– nopoderrors– css = <URL>…
NAME poconflicts – Conflict finder for Gettext PO localization files. SYNOPSIS poconflicts [–version] [-h|–help] [–manpage] [–progress PROGRESS] [–errorlevel ERRORLEVEL] [-i|–input] INPUT [-x|–exclude EXCLUDE] [-o|–output] OUTPUT [-I|–ignore-case] [-v|–invert] [–accelerator ACCELERATORS] DESCRIPTION See: http://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/poconflicts.html for examples and usage instructions. OPTIONS –version show program’s version number and exit -h/–help show this help message and exit –manpage output a…
NAME pocompile – Compile XLIFF and Gettext PO localization files into Gettext MO (Machine Object) files. SYNOPSIS pocompile [–version] [-h|–help] [–manpage] [–progress PROGRESS] [–errorlevel ERRORLEVEL] [-i|–input] INPUT [-x|–exclude EXCLUDE] [-o|–output] OUTPUT [-S|–timestamp] [–fuzzy] [–nofuzzy] DESCRIPTION See: http://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/pocompile.html for examples and usage instructions. OPTIONS –version show program’s version number and exit -h/–help show this help message…
NAME poclean – Produces a clean file from an unclean file (Trados/Wordfast) by stripping out the tw4win indicators. SYNOPSIS poclean [–version] [-h|–help] [–manpage] [–progress PROGRESS] [–errorlevel ERRORLEVEL] [-i|–input] INPUT [-x|–exclude EXCLUDE] [-o|–output] OUTPUT [-S|–timestamp] DESCRIPTION This does not convert an RTF file to PO/XLIFF, but produces the target file with only the target text in…
NAME po4apod-display-po – man display of a translated POD file according to a PO SYNOPSIS po4apod-display-po -p PO_FILE -m POD_FILE [-o PO4A_OPT] DESCRIPTION po4apod-display-po can be used by a translator who wants to check how the man page, generated from a POD file, being translated in a PO will be displayed. Generally, POD file is only…
NAME po4aman-display-po – display a translated man page according to a PO SYNOPSIS po4aman-display-po -p PO_FILE [-m MASTER_FILE] [-o PO4A_OPT] DESCRIPTION po4aman-display-po can be used by a translator who wants to check how the man page being translated in a PO will be displayed. The manual page must be in one of the formats supported by the…
NAME po4a – update both the po files and translated documents in one shot SYNOPSIS po4a [options] <config_file> DESCRIPTION The po4a (po for anything) project goal is to ease translations (and more interestingly, the maintenance of translations) using gettext tools on areas where they were not expected like documentation. The "po4a" program is in charge…
NAME po4a-updatepo – update the translation (in po format) of documentation SYNOPSIS po4a-updatepo -f <fmt> (-m <master.doc>)+ (-p <XX.po>)+ (XX.po are the outputs, all others are inputs) DESCRIPTION The po4a (po for anything) project goal is to ease translations (and more interestingly, the maintenance of translations) using gettext tools on areas where they were not…
NAME po4a-translate – convert a po file back to documentation format SYNOPSIS po4a-translate -f <fmt> -m <master.doc> -p <XX.po> -l <XX.doc> (XX.doc is the output, all others are inputs) DESCRIPTION The po4a (po for anything) project goal is to ease translations (and more interestingly, the maintenance of translations) using gettext tools on areas where they…
NAME po4a-normalize – normalize a documentation file by parsing it in po4a, and writing it back SYNOPSIS po4a-normalize -f <fmt> <master.doc> DESCRIPTION The po4a (po for anything) project goal is to ease translations (and more interestingly, the maintenance of translations) using gettext tools on areas where they were not expected like documentation. The "po4a-normalize" script…
NAME po4a-gettextize – convert an original file (and its translation) to a po file SYNOPSIS po4a-gettextize -f <fmt> -m <master.doc> [-l <XX.doc>] -p <XX.po> (XX.po is the output, all others are inputs) DESCRIPTION The po4a (po for anything) project goal is to ease translations (and more interestingly, the maintenance of translations) using gettext tools on…
NAME po4a-build – build translated documentation SYNOPSIS po4a-build [-f | –file FILE] [–pot-only] po4a-build [-? | -h | –help | –version] DESCRIPTION po4a-build is intended to make it as easy to produce translated documentation as it can be to produce the current untranslated content. When po4a prepares the translated content as POD or DocBook XML,…