Convert POD to MARKUA
Turn POD files into MARKUA. A Markua manuscript with headings, lists, tables, links and footnotes; a table with merged cells or several paragraphs in a cell becomes a [TABLE] line.
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 a Markua manuscript.Headings, lists, tables, links and footnotes carry over into one Markua file.
What you get
One Markua file, the format Leanpub publishes books from. Headings, lists, tables, links and footnotes from the POD are written as their Markua equivalents.
Verbatim paragraphs become code, so sample scripts and command lines stay as code in the manuscript.
What changes or is dropped
A table with merged cells, or with several paragraphs in a cell, becomes a [TABLE] line instead of a table.
Links to other manual pages keep only their name. Paragraphs marked with =for comment are dropped.
Blocks opened with =begin for HTML pass through only where HTML can be kept. Elsewhere they are left out.
POD and MARKUA.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
Markua
Markua, the Markdown dialect Leanpub publishes books from.
- Extensions
- .markua
- MIME type
- text
/x -markua - Kind
- Text and data
In your code.The same POD to MARKUA conversion through the API, for your app or your agent.
$ cv convert report.pod report.markua$ cv convert report.pod report.markuaQuestions.What people ask about POD to MARKUA.
Yes. Verbatim paragraphs in the POD become code in the Markua file.
Ordinary tables stay tables. A table with merged cells or several paragraphs in a cell becomes a [TABLE] line.
No. Paragraphs marked with =for comment are dropped.
They keep only the name of the page. The link itself is not kept.