Convert POD to ASCIIDOC
Turn POD files into ASCIIDOC. An AsciiDoc 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 manuals as AsciiDoc.Headings, lists, tables, links and footnotes carry over into one AsciiDoc file.
What you get
One AsciiDoc document built from your POD file. Headings, lists, tables, links and footnotes are written in AsciiDoc markup.
Verbatim paragraphs become code, so sample snippets in a module's docs stay set apart from the text around them.
What changes
Links to other manual pages keep only their name. The target of the link is not carried over.
Paragraphs marked with =for comment are dropped, so notes meant only for the POD source do not show up in the AsciiDoc.
HTML blocks
A =begin block for HTML passes through only where HTML can be kept. Where HTML cannot be kept, the block does not appear in the output.
For more routes from this format, see every POD conversion. To see what else produces AsciiDoc, see every ASCIIDOC conversion.
POD and ASCIIDOC.What each format is.
The formats
Perl POD
Plain Old Documentation, the markup of Perl manuals and module docs.
- Extensions
- .pod
- MIME type
- text
/x -pod - Kind
- Text and data
AsciiDoc
AsciiDoc, the markup of many software manuals.
- Extensions
- .adoc .asciidoc
- MIME type
- text
/x -asciidoc - Kind
- Text and data
In your code.The same POD to ASCIIDOC conversion through the API, for your app or your agent.
$ cv convert report.pod report.adoc$ cv convert report.pod report.adocQuestions.What people ask about POD to ASCIIDOC.
Yes. Tables and footnotes are part of the AsciiDoc document that comes out, along with headings, lists and links.
Verbatim paragraphs become code in the AsciiDoc.
No. Paragraphs marked with =for comment are dropped.
They keep only their name. The rest of the link is not kept.