Convert POD to MS
Turn POD files into MS. A groff ms document with headings, lists, tables and footnotes; link addresses are dropped, and groff prints it with -ms -t -e.
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 documentation as a groff ms file.Headings, lists, tables and footnotes carry over. Link addresses do not.
What you get
One groff ms document made from your POD file. Headings, lists, tables and footnotes are written with the ms macros, so groff can print the result as a paper or report.
Verbatim paragraphs become code in the output. groff prints the file with -ms -t -e.
What changes or is dropped
Link addresses are dropped, and only the link text stays. A link to another manual page keeps only the name of that page.
Paragraphs marked with =for comment are left out. A =begin block for HTML passes through only where HTML can be kept, so it does not appear elsewhere.
POD and MS.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
groff ms
Documents in the ms macros of troff and groff, which print papers and reports with groff -ms.
- Extensions
- .ms
- MIME type
- text
/x -troff -ms - Kind
- Text and data
In your code.The same POD to MS conversion through the API, for your app or your agent.
$ cv convert report.pod report.ms$ cv convert report.pod report.msQuestions.What people ask about POD to MS.
Use groff with -ms -t -e. The ms macros format the document, and the other two flags are the ones the output is set up for.
Not their addresses. Link addresses are dropped. A link to another manual page keeps only its name.
They become code in the ms file.
No. Paragraphs marked with =for comment are dropped.