Convert POD to IPYNB
Turn POD files into IPYNB. A Jupyter notebook with the text in Markdown cells; only code blocks with the class code become code cells, and outputs are empty.
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 a notebook.The text becomes Markdown cells. Verbatim paragraphs become code.
What you get
One Jupyter notebook with the text of your POD file in Markdown cells. You can open it, read it and add to it like any other notebook.
Verbatim paragraphs, the indented blocks used for examples, become code. Only code blocks with the class code become code cells, and the outputs of those cells are empty.
What changes or is left out
Links to other manual pages keep only their name, so the link itself does not carry over.
Paragraphs marked with =for comment are dropped. Blocks opened with =begin for HTML pass through only where HTML can be kept.
Where to go next
The notebook is one file. To see other things you can do with these formats, look at every POD conversion or every IPYNB conversion.
POD and IPYNB.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
Jupyter Notebook
Jupyter notebooks. Code cells, their outputs and Markdown notes in one JSON file.
- Extensions
- .ipynb
- MIME type
- application
/x -ipynb +json - Kind
- Text and data
In your code.The same POD to IPYNB conversion through the API, for your app or your agent.
$ cv convert report.pod report.ipynb$ cv convert report.pod report.ipynbQuestions.What people ask about POD to IPYNB.
No. The outputs of code cells are empty.
Verbatim paragraphs become code. Only code blocks with the class code become code cells.
Only the name is kept. The link itself is not.
No. They are dropped.