Convert POD to RST

Turn POD files into reStructuredText. A reStructuredText document with headings, lists, tables, links and footnotes.

Converted in an isolated sandbox on our serversDeleted after 24 hours

Drop POD files on the dialor turn it to pick what to do

Perl documentation as reStructuredText.Headings, lists, tables, links and footnotes carry over into one RST file.

  1. What you get

    One reStructuredText file made from your POD. Headings, lists, tables, links and footnotes are written in RST markup, so the document works where Python documentation and Sphinx are used.

    Verbatim paragraphs become code, so indented examples stay as code in the output.

  2. What changes or is dropped

    Links to other manual pages keep only their name. The link target is not carried over.

    Paragraphs marked with =for comment are dropped, so notes meant only for the POD source do not appear in the RST.

    Blocks opened with =begin for HTML pass through only where HTML can be kept. Where it cannot be kept, the block is left out.

POD and RST.What each format is.

The formats

From · POD

Perl POD

Plain Old Documentation, the markup of Perl manuals and module docs.

Extensions
.pod
MIME type
text/x-pod
Kind
Text and data
To · RST

reStructuredText

reStructuredText, the markup of Python documentation and Sphinx.

Extensions
.rst
MIME type
text/x-rst
Kind
Text and data

In your code.The same POD to RST conversion through the API, for your app or your agent.

terminal
$ cv convert report.pod report.rst
$ cv convert report.pod report.rst

Questions.What people ask about POD to RST.

01OF 04

Yes. Verbatim paragraphs in the POD become code in the RST.

They keep only the name of the page. The rest of the link is not kept.

No. Paragraphs marked with =for comment are dropped.

Yes. Tables and footnotes are part of the RST file, along with headings, lists and links.

More conversions.Other ways in and out of POD and RST.