Convert TEXTILE to MD
Turn TEXTILE files into Markdown. GitHub Markdown with headings, lists, tables, code, quotes, footnotes and links, keeping every line break inside a paragraph as Textile does.
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 Markdown.Headings, lists, tables, code and links come across as GitHub Markdown.
What you get
One MD file in GitHub Markdown. Headings, lists, tables, code, quotes, footnotes and links are written in their Markdown forms.
Line breaks inside a paragraph stay where they are, as they do in Textile. A line you broke by hand is still broken in the result.
What changes
Cell spans are not kept. A table cell that stretches across several columns or rows in Textile does not stretch in the Markdown table.
Blocks that carry styling in Textile become HTML blocks. The content stays, written as HTML inside the Markdown file.
Going the other way
To turn Markdown back into Textile, use MD to TEXTILE. To see the other conversions for this format, there is a page for every TEXTILE conversion.
TEXTILE and MD.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
Markdown
Plain text with light markup for headings, lists, links and code. What agents and developers write in.
- Extensions
- .md .markdown .mdown
- MIME type
- text
/markdown - Kind
- Text and data
In your code.The same TEXTILE to MD conversion through the API, for your app or your agent.
$ cv convert report.textile report.md$ cv convert report.textile report.mdQuestions.What people ask about TEXTILE to MD.
Yes. Tables come out as Markdown tables. Cell spans are not kept.
Every line break inside a paragraph is kept, as Textile treats it.
They become HTML blocks in the Markdown file.
Yes. Footnotes and links are both written in Markdown form.