Convert POD to MD
Turn POD files into Markdown. GitHub Markdown 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 docs as GitHub Markdown.Headings, lists, tables, links and footnotes carry over from your POD file.
What you get
One Markdown file in the GitHub flavor. Headings, lists, tables, links and footnotes are written as their Markdown forms, so the manual reads as normal Markdown text.
Verbatim paragraphs become code, so sample code in your module docs stays code.
What changes or is dropped
Links to other manual pages keep only their name. The link itself is not kept.
Paragraphs marked with =for comment are dropped, so notes meant only for the author do not show up in the Markdown.
Blocks opened with =begin for HTML pass through only where HTML can be kept. Where it cannot, they do not appear in the output.
POD and MD.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
Markdown
Plain text with light markup for headings, lists, links and code. What agents and developers write in.
- Extensions
- .md .markdown .mdown
- MIME type
- text
/markdown - Kind
- Text and data
In your code.The same POD to MD conversion through the API, for your app or your agent.
$ cv convert report.pod report.md$ cv convert report.pod report.mdQuestions.What people ask about POD to MD.
Yes. Verbatim paragraphs in the POD become code in the Markdown.
Only the name of the page is kept. The link is not carried over.
No. They are dropped.
Yes. Once you have the Markdown files, you can merge MD into a single file.