Convert TEXTILE to MUSE
Turn TEXTILE files into MUSE. An Emacs Muse document with headings, lists, tables, links and footnotes.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop TEXTILE files on the dialor turn it to pick what to do
Textile turned into Muse markup.You get one Muse file with your headings, lists, tables, links and footnotes.
What you get
A single MUSE file, the markup used by Emacs Muse and Amusewiki. Headings, lists, tables, links and footnotes from the TEXTILE source are written out in Muse form.
Line breaks inside a paragraph are kept, the way Textile treats them. A paragraph that you wrote over several lines stays on several lines.
What changes
Cell spans in tables are not kept. A cell that stretches across columns or rows in the TEXTILE source does not stretch in the MUSE file.
Images stay as links. The picture is not embedded in the output; the Muse file points to it.
Going the other way
To turn Muse markup back into Textile, use MUSE to TEXTILE. For other conversions of this format, see every TEXTILE conversion.
TEXTILE and MUSE.What each format is.
The formats
Textile
Textile markup, once common in Rails apps and Redmine.
- Extensions
- .textile
- MIME type
- text
/x -textile - Kind
- Text and data
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
In your code.The same TEXTILE to MUSE conversion through the API, for your app or your agent.
$ cv convert report.textile report.muse$ cv convert report.textile report.museQuestions.What people ask about TEXTILE to MUSE.
Yes. Headings and lists are kept and written in Muse markup.
Yes. Every line break inside a paragraph is kept, as Textile does.
They stay as links. The images are not embedded in the Muse file.
No. Cell spans are not kept, so a merged cell is not merged in the output.