Convert MUSE to TEXINFO
Turn MUSE 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 MUSE files on the dialor turn it to pick what to do
A Texinfo manual from your Muse text.Each top-level heading becomes a chapter with its own node.
What you get
One Texinfo file with your lists, tables, links and footnotes. Each top-level heading becomes a chapter with its own node and its own menu entry.
What changes
Verse keeps its line breaks. Centered and right-aligned blocks become plain paragraphs, so their alignment is not kept.
Comments are dropped and do not appear in the Texinfo file. Images stay as links.
MUSE and TEXINFO.What each format is.
The formats
Muse
Emacs Muse and Amusewiki markup, used for books and essays in online libraries.
- Extensions
- .muse
- MIME type
- text
/x -muse - 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 MUSE to TEXINFO conversion through the API, for your app or your agent.
$ cv convert report.muse report.texi$ cv convert report.muse report.texiQuestions.What people ask about MUSE to TEXINFO.
A chapter. Each one gets its own node and a menu entry.
Yes. Footnotes are part of what the Texinfo manual keeps, along with lists, tables and links.
No. Centered and right-aligned blocks become plain paragraphs.
They are dropped. Comments in the Muse file do not appear in the Texinfo output.