Convert TEXTILE to HTML
Turn TEXTILE files into HTML. A standalone page titled after the file, keeping headings, lists, tables, code, quotes, footnotes and links, and 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 as a standalone HTML page.Headings, lists, tables, code and links carry over. Cell spans and image files do not.
What you get
One HTML file, a standalone page titled after the file. It keeps headings, lists, tables, code, quotes, footnotes and links from the Textile source.
Every line break inside a paragraph is kept, as Textile does it.
What changes
Block classes and styles become attributes on the matching elements.
Cell spans are not kept, so a table cell that spans several columns or rows does not span them in the HTML.
Images
Images stay links to files. Those files were not uploaded, so the page points to them but does not contain them. Put the image files where the links expect them if you want the pictures to show.
Going the other way
To turn a page back into markup, use HTML to TEXTILE. It is a separate conversion with its own results.
TEXTILE and HTML.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
HTML
The markup of web pages. Text, links and structure, usually with CSS and images alongside.
- Extensions
- .html .htm
- MIME type
- text
/html - Kind
- Text and data
In your code.The same TEXTILE to HTML conversion through the API, for your app or your agent.
$ cv convert report.textile report.html$ cv convert report.textile report.htmlQuestions.What people ask about TEXTILE to HTML.
Yes. The page is titled after the file.
No. Images stay links to files that were not uploaded, so the HTML does not hold the pictures.
Yes. Footnotes and tables are kept, but cell spans in tables are not.
They become attributes in the HTML.