Convert MAN to TEXINFO
Turn MAN 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 MAN files on the dialor turn it to pick what to do
A Texinfo manual from a man page.Headings, lists, tables and fonts carry over into one Texinfo file.
What you get
One Texinfo file. Each top-level heading becomes a chapter with its own node and menu entry. Sections become headings.
Tagged paragraphs become definition lists. Bold and italic fonts, examples and tables are kept. Lists, links and footnotes come through as well.
What it leaves behind
The section number and the header and footer fields are dropped. They are not copied into the Texinfo file.
Pages written in the BSD mdoc macros keep only their running text. Their other content is not carried over.
Options
This conversion has no options. There is nothing to set before you convert.
If you want to see other conversions, browse every MAN conversion or every TEXINFO conversion.
MAN and TEXINFO.What each format is.
The formats
Man Page
Unix manual pages in troff.
- Extensions
- .man
- MIME type
- text
/troff - 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 MAN to TEXINFO conversion through the API, for your app or your agent.
$ cv convert report.man report.texi$ cv convert report.man report.texiQuestions.What people ask about MAN to TEXINFO.
Yes. Each top-level heading becomes a chapter with its own node and menu entry.
They become definition lists in the Texinfo file.
Yes. Bold and italic fonts are kept, along with examples and tables.
Pages written in the BSD mdoc macros keep only their running text.