Convert POD to TEXINFO
Turn POD files into TEXINFO. A Texinfo manual with lists, tables, links and footnotes; each top-level heading becomes a chapter with its own node and menu entry.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop POD files on the dialor turn it to pick what to do
A Texinfo manual from your POD.Lists, tables, links and footnotes carry over into one Texinfo file.
What you get
One Texinfo file with the structure of the manual. Each top-level heading becomes a chapter with its own node and a menu entry, so the manual has a menu to move through.
Lists, tables, links and footnotes are kept as Texinfo lists, tables, links and footnotes.
What changes
Verbatim paragraphs become code. Links to other manual pages keep only their name, so the link itself is not kept.
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 TEXINFO.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
Texinfo
Texinfo, the source of GNU manuals that becomes Info pages, HTML and printed books.
- Extensions
- .texi .texinfo
- MIME type
- application
/x -texinfo - Kind
- Text and data
In your code.The same POD to TEXINFO conversion through the API, for your app or your agent.
$ cv convert report.pod report.texi$ cv convert report.pod report.texiQuestions.What people ask about POD to TEXINFO.
Each top-level heading becomes a chapter with its own node and menu entry.
They keep only the name of the page. The link is not kept.
No. Paragraphs marked with =for comment are dropped.
No options are available for this conversion. It produces one file. See every POD conversion for other conversions from POD.